[Tarantool-patches] [PATCH] box: remove unicode_ci for functions

[Nikita Pettik]

On 02 Dec 10:07, Konstantin Osipov wrote:
> * Vladislav Shpilevoy <v.shpilevoy at tarantool.org> [19/12/01 19:29]:
> > >> Unicode_ci collation breaks the general
> > >> rule for objects naming, so we remove it
> > >> in version 2.3.1
> > > 
> > > The code works according to RFC.
> > > 
> > > There is a justification for this behaviour in RFC.
> 
> Please see my reply with an explanation. The RFC was  written
> presuming https://github.com/tarantool/tarantool/issues/4467 
> will be fixed. 

According to milestone (which is 'feature'), it is not going to be
implemented soon. What is more, there's even no clearly stated proposal
or RFC without contradictions.

> The current way of uppercasing is broken - it is hard to use,
> and people hit the problem almost immediately, especially newbies.
> 
> Instead of fixing the "inconsistency", one should fix 4467

Just for the record, I have to say that I agree with Vlad and Chris.
Function's name featuring unicode_ci collation at least seem to be
strange. RFC says:

'''
To avoid name clash, we will reserve these names by adding entries for them in _func system space.
'''

That's all.

I can't figure out what did author really mean by 'name clash'.
We are able to create two different objects (of any kind: space,
trigger etc) with the same in terms of case-insensetive collation
(e.g. "t1" and "T1"). Why this rule should be violated for functions?