From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp44.i.mail.ru (smtp44.i.mail.ru [94.100.177.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 307AC46971A for ; Sun, 1 Dec 2019 17:12:46 +0300 (MSK) From: k.sosnin Message-Id: <6241F536-7732-4E2F-ACC8-27A17F3BD5EF@tarantool.org> Content-Type: multipart/alternative; boundary="Apple-Mail=_14E08EE3-C7F5-469D-9DA0-811AA4FE0E5B" Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Date: Sun, 1 Dec 2019 17:12:44 +0300 In-Reply-To: <20191130203439.GA23478@atlas> References: <20191129233922.36600-1-k.sosnin@tarantool.org> <20191130203439.GA23478@atlas> 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: Konstantin Osipov Cc: tarantool-patches@dev.tarantool.org --Apple-Mail=_14E08EE3-C7F5-469D-9DA0-811AA4FE0E5B Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii > The code works according to RFC. > > There is a justification for this behaviour in RFC. Quote from RFC: To avoid name clash, we will reserve these names by adding entries for them in _func system space. _func.name index collation will change to use unicode_ci. All built-ins will be added to the bootstrap snapshot. It is not really mentioned why it is necessary to change the collation. Also, there is no conflict with SQL functions as long as every query gets upper-cased. --Apple-Mail=_14E08EE3-C7F5-469D-9DA0-811AA4FE0E5B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

The code works = according to RFC.

There is a justification = for this behaviour in RFC.

Quote from RFC:

To avoid name clash, we will = reserve 
these names by adding entries for them
in _func system = space. _func.name
index collation will change
to use unicode_ci. All built-ins
will be added to = the bootstrap snapshot.

It is not really mentioned why it is = necessary
to change the collation. Also, there is no conflict
with SQL = functions as long as every query gets upper-cased.
= --Apple-Mail=_14E08EE3-C7F5-469D-9DA0-811AA4FE0E5B--