Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: "n.pettik" <korablev@tarantool.org>, tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH 1/2] sql: derive collation for built-in functions
Date: Thu, 7 Mar 2019 17:40:24 +0300	[thread overview]
Message-ID: <cc7727e6-2421-a417-35c7-beeea01cd6a4@tarantool.org> (raw)
In-Reply-To: <7CC1E113-479D-46FC-9A6F-6BE73E918FE7@tarantool.org>



>> For user-defined functions and for
>> bind parameters it does not fit. How can you determine
>> a function's result collation, if it is not builtin, and
>> does not depend on arguments?
> 
> In no way. We can extend signature of sql_create_function
> and allow to pass collation to be applied to returning value.
> But I am not sure that we should do this. Anyway, it wouldn't
> help us with the initial issue: in our case collation is dependent
> on one of arguments, so it *dynamically* changes. Hence, I
> guess these problems are barely related.
> 
> Also, inlining comment from P.Gulutzan:
> (https://github.com/tarantool/tarantool/issues/3932)
> 
> ‘’'
> 
> It is true that user-defined functions will not know some things about
> what an SQL caller is passing. We don't promise that they will, so I
> think it is okay that it is the caller's responsibility to make sure
> relevant information is passed explicitly. A possible issue is that the
> function cannot use the utf8 module for all possible collations, but
> that is not an SQL issue.
> 
> ‘''

So do you mean that any string returned from a user defined function
always has no any collation?

I do not talk about Lua functions only. In future we are going to
introduce SQL functions.

> 
>> Does SQL standard allow to define user functions without
>> a runtime defined collation? If SQL standard does not define
>> SQL functions at all, then what other vendors do with that
>> problem?
> 
> There’s no such opportunity in ANSI, if I’m not mistaking.
> Generally speaking, other vendors have procedural SQL.
> And since PSQL is a part of SQL, there are no such problems:
> collation is a part of string-like types.
> 

It contradicts with your way of collation return. If PSQL states
that collation is a part of string-like type, then it is
possible to implement a function doing something like this:

     function my_func()
         if (rand() % 2 == 0) then
             return 'abc' collate 'unicode_ci';
         return 'abc' collate 'unicode';
     end;

(I do not know PSQL syntax - the code above is pseudo- ).

As I see, now we have no runtime defined collations at all -
all of them are known during compilation. Struct Mem, storing
function return value, even has no collation member. I guess,
we can not implement runtime collations now.

  reply	other threads:[~2019-03-07 14:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 18:01 [tarantool-patches] [PATCH 0/2] Add collation to built-in funcs and fix HAVING clause with aggregate Nikita Pettik
2019-02-21 18:01 ` [tarantool-patches] [PATCH 1/2] sql: derive collation for built-in functions Nikita Pettik
2019-02-25 12:58   ` [tarantool-patches] " Vladislav Shpilevoy
2019-02-25 18:32     ` n.pettik
2019-03-07 14:40       ` Vladislav Shpilevoy [this message]
2019-03-11  8:04         ` Konstantin Osipov
2019-02-21 18:01 ` [tarantool-patches] [PATCH 2/2] sql: fix code generation for aggregate in HAVING clause Nikita Pettik
2019-02-25 12:58   ` [tarantool-patches] " Vladislav Shpilevoy
2019-02-25 18:33     ` n.pettik
2019-03-04 12:14       ` n.pettik
2019-03-04 12:52         ` Vladislav Shpilevoy
2019-03-07 14:40 ` [tarantool-patches] Re: [PATCH 0/2] Add collation to built-in funcs and fix HAVING clause with aggregate Vladislav Shpilevoy
2019-03-11 15:49 ` Kirill Yukhin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cc7727e6-2421-a417-35c7-beeea01cd6a4@tarantool.org \
    --to=v.shpilevoy@tarantool.org \
    --cc=korablev@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH 1/2] sql: derive collation for built-in functions' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox