From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f195.google.com (mail-lj1-f195.google.com [209.85.208.195]) (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 EA62346971A for ; Mon, 2 Dec 2019 10:07:16 +0300 (MSK) Received: by mail-lj1-f195.google.com with SMTP id s22so19691987ljs.7 for ; Sun, 01 Dec 2019 23:07:16 -0800 (PST) Date: Mon, 2 Dec 2019 10:07:15 +0300 From: Konstantin Osipov Message-ID: <20191202070715.GA27802@atlas> References: <20191129233922.36600-1-k.sosnin@tarantool.org> <20191130203439.GA23478@atlas> <13437800-f8ec-1964-f7d7-a01581e242ad@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <13437800-f8ec-1964-f7d7-a01581e242ad@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH] box: remove unicode_ci for functions List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladislav Shpilevoy Cc: tarantool-patches@dev.tarantool.org * Vladislav Shpilevoy [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. 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 -- Konstantin Osipov, Moscow, Russia