From: Kirill Yukhin <kyukhin@tarantool.org>
To: tarantool-patches@freelists.org
Cc: v.shpilevoy@tarantool.org, Nikita Pettik <korablev@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v2 0/3] Change collation compatibility rules according to ANSI SQL
Date: Thu, 15 Nov 2018 14:24:40 +0300 [thread overview]
Message-ID: <20181115112440.zqzf2xlzyfjeso2v@tarantool.org> (raw)
In-Reply-To: <cover.1542066357.git.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
prev parent reply other threads:[~2018-11-15 11:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 0:07 [tarantool-patches] " Nikita Pettik
2018-11-13 0:07 ` [tarantool-patches] [PATCH v2 1/3] sql: do not add explicit <COLLATE "BINARY"> clause Nikita Pettik
2018-11-13 0:07 ` [tarantool-patches] [PATCH v2 2/3] Introduce "none" and "binary" collations Nikita Pettik
2018-11-13 12:02 ` [tarantool-patches] " Vladislav Shpilevoy
2018-11-13 22:37 ` n.pettik
2018-11-14 11:52 ` Vladislav Shpilevoy
2018-11-14 20:59 ` n.pettik
2018-11-15 11:04 ` Vladislav Shpilevoy
2018-11-13 0:07 ` [tarantool-patches] [PATCH v2 3/3] sql: change collation compatibility rules Nikita Pettik
2018-11-13 12:02 ` [tarantool-patches] " Vladislav Shpilevoy
2018-11-13 22:37 ` n.pettik
2018-11-15 11:24 ` Kirill Yukhin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181115112440.zqzf2xlzyfjeso2v@tarantool.org \
--to=kyukhin@tarantool.org \
--cc=korablev@tarantool.org \
--cc=tarantool-patches@freelists.org \
--cc=v.shpilevoy@tarantool.org \
--subject='[tarantool-patches] Re: [PATCH v2 0/3] Change collation compatibility rules according to ANSI SQL' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox