From: "Мерген Имеев" <imeevma@tarantool.org> To: tarantool-patches@freelists.org Subject: [tarantool-patches] Re: [tarantool-patches] Re: [PATCH v2 1/1] sql: COLLATE after LIMIT throws an error Date: Mon, 21 May 2018 19:50:55 +0300 [thread overview] Message-ID: <1526921455.373334107@f455.i.mail.ru> (raw) In-Reply-To: <f123807c-1f14-b0e7-a7ec-345cf9c431ea@tarantool.org> [-- Attachment #1: Type: text/plain, Size: 4591 bytes --] >Понедельник, 21 мая 2018, 18:27 +03:00 от Vladislav Shpilevoy <v.shpilevoy@tarantool.org>: > >Thanks a lot! > >But please, apply this diff: > >diff --git a/src/box/sql/select.c b/src/box/sql/select.c >index 7a7728992..0b610dca7 100644 >--- a/src/box/sql/select.c >+++ b/src/box/sql/select.c >@@ -1994,8 +1994,10 @@ computeLimitRegisters(Parse * pParse, Select * p, int iBreak) > assert(p->pOffset == 0 || p->pLimit != 0); > if (p->pLimit) { > if((p->pLimit->flags & EP_Collate) != 0 || >- (p->pOffset && (p->pOffset->flags & EP_Collate) != 0)) { >- sqlite3ErrorMsg(pParse, "near \"COLLATE\": syntax error"); >+ (p->pOffset != NULL && >+ (p->pOffset->flags & EP_Collate) != 0)) { >+ sqlite3ErrorMsg(pParse, "near \"COLLATE\": "\ >+ "syntax error"); > return; > } > p->iLimit = iLimit = ++pParse->nMem; > >In your patch sqlite3ErrorMsg was out of 80 symbols, and pointer p->pOffset must be checked >on != NULL explicitly. (I see, that other SQLite3 code does not this, but we will fix >this gradually). Done. > > >After this the patch LGTM. > commit 8ae83069671e7384c70523f4eda201d4815dba26 Author: ImeevMA <imeevma@tarantool.org> Date: Mon May 21 16:21:57 2018 +0300 sql: COLLATE after LIMIT throws an error Originally, SQLite3 execute queries with COLLATE after LIMIT like "SELECT * FROM test LIMIT N COLLATE not_exist" and queries without COLLATE like "SELECT * FROM test LIMIT N" the same way. From this patch on queries with COLLATE after LIMIT or OFFSET throws a syntax error. Closes #3010 diff --git a/src/box/sql/select.c b/src/box/sql/select.c index 29075d5..fc1da27 100644 --- a/src/box/sql/select.c +++ b/src/box/sql/select.c @@ -1993,6 +1993,13 @@ computeLimitRegisters(Parse * pParse, Select * p, int iBreak) sqlite3ExprCacheClear(pParse); assert(p->pOffset == 0 || p->pLimit != 0); if (p->pLimit) { + if((p->pLimit->flags & EP_Collate) != 0 || + (p->pOffset != NULL && + (p->pOffset->flags & EP_Collate) != 0)) { + sqlite3ErrorMsg(pParse, "near \"COLLATE\": "\ + "syntax error"); + return; + } p->iLimit = iLimit = ++pParse->nMem; v = sqlite3GetVdbe(pParse); assert(v != 0); diff --git a/test/sql/collation.result b/test/sql/collation.result new file mode 100644 index 0000000..3a4f81f --- /dev/null +++ b/test/sql/collation.result @@ -0,0 +1,41 @@ +remote = require('net.box') +--- +... +-- gh-3010: COLLATE after LIMIT should throw an error +-- All of these tests should throw error "near "COLLATE": syntax error" +box.sql.execute("SELECT 1 LIMIT 1 COLLATE BINARY;") +--- +- error: 'near "COLLATE": syntax error' +... +box.sql.execute("SELECT 1 LIMIT 1 COLLATE BINARY OFFSET 1;") +--- +- error: 'near "COLLATE": syntax error' +... +box.sql.execute("SELECT 1 LIMIT 1 OFFSET 1 COLLATE BINARY;") +--- +- error: 'near "COLLATE": syntax error' +... +box.sql.execute("SELECT 1 LIMIT 1, 1 COLLATE BINARY;") +--- +- error: 'near "COLLATE": syntax error' +... +box.sql.execute("SELECT 1 LIMIT 1 COLLATE BINARY, 1;") +--- +- error: 'near "COLLATE": syntax error' +... +box.schema.user.grant('guest','read,write,execute', 'universe') +--- +... +cn = remote.connect(box.cfg.listen) +--- +... +cn:execute('select 1 limit ? collate not_exist', {1}) +--- +- error: 'Failed to execute SQL statement: near "COLLATE": syntax error' +... +cn:close() +--- +... +box.schema.user.revoke('guest', 'read,write,execute', 'universe') +--- +... diff --git a/test/sql/collation.test.lua b/test/sql/collation.test.lua new file mode 100644 index 0000000..fe8c1ba --- /dev/null +++ b/test/sql/collation.test.lua @@ -0,0 +1,19 @@ +remote = require('net.box') + +-- gh-3010: COLLATE after LIMIT should throw an error + +-- All of these tests should throw error "near "COLLATE": syntax error" +box.sql.execute("SELECT 1 LIMIT 1 COLLATE BINARY;") +box.sql.execute("SELECT 1 LIMIT 1 COLLATE BINARY OFFSET 1;") +box.sql.execute("SELECT 1 LIMIT 1 OFFSET 1 COLLATE BINARY;") +box.sql.execute("SELECT 1 LIMIT 1, 1 COLLATE BINARY;") +box.sql.execute("SELECT 1 LIMIT 1 COLLATE BINARY, 1;") + + +box.schema.user.grant('guest','read,write,execute', 'universe') +cn = remote.connect(box.cfg.listen) + +cn:execute('select 1 limit ? collate not_exist', {1}) + +cn:close() +box.schema.user.revoke('guest', 'read,write,execute', 'universe') [-- Attachment #2: Type: text/html, Size: 6194 bytes --]
next prev parent reply other threads:[~2018-05-21 16:51 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-21 14:36 [tarantool-patches] " ImeevMA 2018-05-21 14:45 ` [tarantool-patches] " Vladislav Shpilevoy 2018-05-21 15:16 ` [tarantool-patches] " Мерген Имеев 2018-05-21 15:27 ` Vladislav Shpilevoy 2018-05-21 16:50 ` Мерген Имеев [this message] 2018-05-21 18:26 ` Vladislav Shpilevoy 2018-05-22 7:01 ` 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=1526921455.373334107@f455.i.mail.ru \ --to=imeevma@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [tarantool-patches] Re: [PATCH v2 1/1] sql: COLLATE after LIMIT throws an error' \ /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