From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kostja.osipov@gmail.com>
Received: from mail-lf1-f65.google.com (mail-lf1-f65.google.com
 [209.85.167.65])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by dev.tarantool.org (Postfix) with ESMTPS id 566DA46971A
 for <tarantool-patches@dev.tarantool.org>;
 Fri,  6 Dec 2019 23:17:44 +0300 (MSK)
Received: by mail-lf1-f65.google.com with SMTP id n25so6243682lfl.0
 for <tarantool-patches@dev.tarantool.org>;
 Fri, 06 Dec 2019 12:17:44 -0800 (PST)
Date: Fri, 6 Dec 2019 23:17:18 +0300
From: Konstantin Osipov <kostja.osipov@gmail.com>
Message-ID: <20191206201718.GA7299@atlas>
References: <20191129233922.36600-1-k.sosnin@tarantool.org>
 <20191130203439.GA23478@atlas>
 <13437800-f8ec-1964-f7d7-a01581e242ad@tarantool.org>
 <20191202070715.GA27802@atlas>
 <20191206114244.umbeo556b2atuhjm@tarantool.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20191206114244.umbeo556b2atuhjm@tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH] box: remove unicode_ci for functions
List-Id: Tarantool development patches <tarantool-patches.dev.tarantool.org>
List-Unsubscribe: <https://lists.tarantool.org/mailman/options/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=unsubscribe>
List-Archive: <https://lists.tarantool.org/pipermail/tarantool-patches/>
List-Post: <mailto:tarantool-patches@dev.tarantool.org>
List-Help: <mailto:tarantool-patches-request@dev.tarantool.org?subject=help>
List-Subscribe: <https://lists.tarantool.org/mailman/listinfo/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=subscribe>
To: Kirill Yukhin <kyukhin@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org, Vladislav Shpilevoy <v.shpilevoy@tarantool.org>

* Kirill Yukhin <kyukhin@tarantool.org> [19/12/06 23:09]:
> > > >> 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.
> 
> It was clearly pointed that proposal in #4467 is broken by
> design. Please see [1] for details. Having that said I think
> we should consider the proposal rejected and won't try to invent
> any new workarounds.
> 
> [1] - https://github.com/tarantool/tarantool/issues/4467#issuecomment-527210486 and later.

Even if you think the proposal is broken the problem is there
and needs resolution, not aggravation. 

Re initial proposal being broken I admitted it in the comment.
We'll have to do an incompatible change and violate ANSI - in
order to make the product usable. I suggested to add a
case-insensitive unique index to every system space already.

As to the suggestion being broken - it will allow one to get rid
of uppercase-before-store and be mostly ansi compatible.

It's less broken what we have now.

-- 
Konstantin Osipov, Moscow, Russia
https://scylladb.com