From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: tarantool-patches@freelists.org, "n.pettik" <korablev@tarantool.org> Cc: Roman Khabibov <roman.habibov@tarantool.org> Subject: [tarantool-patches] Re: [PATCH 1/2 v2] test: check that collations isn't ignored in SELECTs Date: Tue, 25 Jun 2019 19:55:39 +0200 [thread overview] Message-ID: <01159864-ba96-a618-4d07-7f250994fcc1@tarantool.org> (raw) In-Reply-To: <F293D168-1837-4483-8016-0FD2E24BF2C0@tarantool.org> On 25/06/2019 19:30, n.pettik wrote: > > >> On 24 Jun 2019, at 13:54, Roman Khabibov <roman.habibov@tarantool.org> wrote: >> >> Add test to check that a new collation isn't ignored regardless >> of a name of a previous one in the following patterns of quries: > > Nit: quries -> queries > >> >> SELECT s COLLATE "unicode_ci" FROM a ORDER BY s COLLATE “unicode_ci" > > Why do you consider this kind of query? What can be wrong with it? That example works, but when the collations are different, according to the standard the last one should be applied, as I remember when I last time checked. Before the patch a wrong collation was used when there are several of them. If under `this kind of query` you mean why 'order by'? - it is just the only request where we can reproduce that. I've tried to find a simpler test, but did not manage. > Specifying collation for result set members doesn’t make much sense btw. > >> >> Also note: It is disallowed to compare strings with different >> collations: ISO/IEC JTC 1/SC 32, Part 2: Foundation, page 531 >> --- >> src/box/sql/resolve.c | 7 +++++++ >> test/sql-tap/collation.test.lua | 19 ++++++++++++++++++- >> 2 files changed, 25 insertions(+), 1 deletion(-) >> >> diff --git a/src/box/sql/resolve.c b/src/box/sql/resolve.c >> index fdf3703da..348b3ea9a 100644 >> --- a/src/box/sql/resolve.c >> +++ b/src/box/sql/resolve.c >> @@ -109,6 +109,13 @@ resolveAlias(Parse * pParse, /* Parsing context */ >> return; >> if (zType[0] != 'G') >> incrAggFunctionDepth(pDup, nSubquery); >> + /* >> + * If there was typed more than one explicit collations in >> + * query, it will be a sequence of left nodes with the >> + * collations in a tree. There is nothing special about >> + * keeping the sequence. Only one collation could be >> + * stored, but the present solution is simpler. >> + */ > > Do not understand how mentioned example is related to this code. > I suppose you might mean example like: > > SELECT s COLLATE “unicode” COLLATE “binary” COLLATE “unicode_ci” … > > Is this syntax allowed by ANSI? If so, which one (first or last) collation must be used? Yes, allowed, the last collation should be used. Probably, Roman, you should include in the commit message a reference to the standard (probably you did, I don't know - the first message in that thread is lost in my copy of our mailing list). > >> if (pExpr->op == TK_COLLATE) { >> pDup = >> sqlExprAddCollateString(pParse, pDup, pExpr->u.zToken);
next prev parent reply other threads:[~2019-06-25 17:54 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <cover.1561372731.git.roman.habibov@tarantool.org> [not found] ` <49f3a1279811efc66c580c6039cf1b890ff37889.1561372731.git.roman.habibov@tarantool.org> 2019-06-25 17:30 ` n.pettik 2019-06-25 17:55 ` Vladislav Shpilevoy [this message] 2019-06-28 13:11 ` Roman Khabibov 2019-06-28 13:13 ` Roman Khabibov 2019-07-02 17:21 ` n.pettik [not found] ` <91edd7e8b72a93c5b5c0592c181576fca98e66fd.1561372731.git.roman.habibov@tarantool.org> 2019-06-25 17:30 ` [tarantool-patches] Re: [PATCH 2/2 v2] sql: allow <COLLATE> only for string-like args n.pettik 2019-06-28 12:57 ` Roman Khabibov 2019-07-02 15:55 ` n.pettik 2019-07-06 1:04 ` Roman Khabibov 2019-07-08 13:38 ` n.pettik 2019-07-16 13:09 ` Kirill Yukhin
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=01159864-ba96-a618-4d07-7f250994fcc1@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=korablev@tarantool.org \ --cc=roman.habibov@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [PATCH 1/2 v2] test: check that collations isn'\''t ignored in SELECTs' \ /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