From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <tarantool-patches-bounce@freelists.org>
Received: from localhost (localhost [127.0.0.1])
	by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 7C26930526
	for <tarantool-patches@freelists.org>; Thu, 15 Nov 2018 06:24:47 -0500 (EST)
Received: from turing.freelists.org ([127.0.0.1])
	by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AbEghvD2T73W for <tarantool-patches@freelists.org>;
	Thu, 15 Nov 2018 06:24:47 -0500 (EST)
Received: from smtp16.mail.ru (smtp16.mail.ru [94.100.176.153])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id 2E5F930525
	for <tarantool-patches@freelists.org>; Thu, 15 Nov 2018 06:24:47 -0500 (EST)
Date: Thu, 15 Nov 2018 14:24:40 +0300
From: Kirill Yukhin <kyukhin@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v2 0/3] Change collation
 compatibility rules according to ANSI SQL
Message-ID: <20181115112440.zqzf2xlzyfjeso2v@tarantool.org>
References: <cover.1542066357.git.korablev@tarantool.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <cover.1542066357.git.korablev@tarantool.org>
Sender: tarantool-patches-bounce@freelists.org
Errors-to: tarantool-patches-bounce@freelists.org
Reply-To: tarantool-patches@freelists.org
List-help: <mailto:ecartis@freelists.org?Subject=help>
List-unsubscribe: <tarantool-patches-request@freelists.org?Subject=unsubscribe>
List-software: Ecartis version 1.0.0
List-Id: tarantool-patches <tarantool-patches.freelists.org>
List-subscribe: <tarantool-patches-request@freelists.org?Subject=subscribe>
List-owner: <mailto:>
List-post: <mailto:tarantool-patches@freelists.org>
List-archive: <http://www.freelists.org/archives/tarantool-patches>
To: tarantool-patches@freelists.org
Cc: v.shpilevoy@tarantool.org, Nikita Pettik <korablev@tarantool.org>

Hello,
On 13 Nov 03:07, Nikita Pettik wrote:
> This patch-set introduces rules for collation compatibility in order to
> restrict usage of different collations within one comparison.
> Originally, SQLite uses doubtful approach: if collations of LHS and RHS
> can not be used together, then collation of LHS is chosen.  Such
> behaviour quite misleading and results in the fact that swap of LHS and
> RHS values may change result of operation.  We've decided to add
> restrictions on collations of LHS and RHS to disallow messing different
> collations as it is stated in ANSI SQL.

I've rebased and checked your patch set into 2.1 branch.

--
Regards, Kirill Yukhin