From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: tarantool-patches@freelists.org, imeevma@tarantool.org Subject: [tarantool-patches] Re: [PATCH v1 18/28] sql: remove SQL_CONSTRAINT errcode Date: Fri, 14 Jun 2019 00:24:55 +0200 [thread overview] Message-ID: <a3433fb4-dbb9-1341-0485-d1365a1dab64@tarantool.org> (raw) In-Reply-To: <40cba82136f5c06632922856f95294616a475b74.1560174553.git.imeevma@gmail.com> Thanks for the patch! I've found 'sql_CONSTRAINT_UNIQUE' in sql-tap/unique.test.lua on line 229. These tests are disabled by 'if 0 > 0', but another comment says, that the issue #2495 fix should have enabled them back. We need to either resurrect these tests, or drop them. Consider my review fixes below and on the branch in a separate commit. ====================================================== diff --git a/src/box/sql/sqlInt.h b/src/box/sql/sqlInt.h index acfeea588..128f5747d 100644 --- a/src/box/sql/sqlInt.h +++ b/src/box/sql/sqlInt.h @@ -3719,17 +3719,16 @@ sql_generate_index_key(struct Parse *parse, struct index *index, int cursor, * ---------- ---------- -------------------------------------- * any ROLLBACK The current transaction is rolled * back and VDBE stops immediately - * with return code of sql_CONSTRAINT. + * with an error. * * any ABORT Back out changes from the current * command only (do not do a complete * rollback) then cause VDBE to return - * immediately with sql_CONSTRAINT. + * immediately with an error. * - * any FAIL VDBE returns immediately with a - * return code of sql_CONSTRAINT. The - * transaction is not rolled back and any - * changes to prior rows are retained. + * any FAIL VDBE returns immediately with an error. + * The transaction is not rolled back and + * any changes to prior rows are retained. * * any IGNORE The attempt in insert or update the * current row is skipped, without diff --git a/test/sql-tap/trigger1.test.lua b/test/sql-tap/trigger1.test.lua index 38d7c5525..bc02d6236 100755 --- a/test/sql-tap/trigger1.test.lua +++ b/test/sql-tap/trigger1.test.lua @@ -511,7 +511,7 @@ test:do_catchsql_test( -- </trigger1-6.3> }) --- verify_ex_errcode trigger1-6.3b sql_CONSTRAINT_TRIGGER +-- Verify the previous test has not deleted anything. test:do_execsql_test( "trigger1-6.4", [[ diff --git a/test/sql-tap/unique.test.lua b/test/sql-tap/unique.test.lua index fbd73a650..358a06f40 100755 --- a/test/sql-tap/unique.test.lua +++ b/test/sql-tap/unique.test.lua @@ -74,7 +74,7 @@ test:do_catchsql_test( -- </unique-1.3> }) --- verify_ex_errcode unique-1.3b sql_CONSTRAINT_PRIMARYKEY +-- Verify the previous test has not inserted anything. test:do_execsql_test( "unique-1.4", [[ @@ -95,7 +95,7 @@ test:do_catchsql_test( -- </unique-1.5> }) --- verify_ex_errcode unique-1.5b sql_CONSTRAINT_UNIQUE +-- Verify the previous test has not inserted anything. test:do_execsql_test( "unique-1.6", [[ @@ -171,7 +171,7 @@ test:do_catchsql_test( -- </unique-2.3> }) --- verify_ex_errcode unique-2.3b sql_CONSTRAINT_UNIQUE +-- Verify the previous test has not inserted anything. test:do_catchsql_test( "unique-2.4", [[ @@ -291,7 +291,6 @@ test:do_catchsql_test( -- </unique-3.4> }) --- verify_ex_errcode unique-3.4b sql_CONSTRAINT_UNIQUE --integrity_check unique-3.5 -- Make sure NULLs are distinct as far as the UNIQUE tests are -- concerned. @@ -405,7 +404,6 @@ test:do_catchsql_test( }) end --- verify_ex_errcode unique-4.10b sql_CONSTRAINT_UNIQUE --integrity_check unique-4.99 -- Test the error message generation logic. In particular, make sure we -- do not overflow the static buffer used to generate the error message. @@ -448,7 +446,4 @@ test:do_catchsql_test( -- </unique-5.2> }) --- verify_ex_errcode unique-5.2b sql_CONSTRAINT_UNIQUE - - test:finish_test()
next prev parent reply other threads:[~2019-06-13 22:24 UTC|newest] Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-10 13:56 [tarantool-patches] [PATCH v1 00/28] sql: Remove SQL error system imeevma 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 01/28] sql: remove field zErrMsg from struct Vdbe imeevma 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 02/28] sql: remove field pErr from struct sql imeevma 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 03/28] sql: remove field errCode " imeevma 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 04/28] sql: remove sqlError() and remove sqlErrorWithMsg() imeevma 2019-06-13 22:25 ` [tarantool-patches] " Vladislav Shpilevoy 2019-06-15 9:45 ` Mergen Imeev 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 05/28] sql: remove unused functions of SQL error system imeevma 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 06/28] sql: disable lookaside system imeevma 2019-06-13 22:25 ` [tarantool-patches] " Vladislav Shpilevoy 2019-06-15 9:47 ` Mergen Imeev 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 07/28] sql: remove SQL_OK error/status code imeevma 2019-06-13 22:24 ` [tarantool-patches] " Vladislav Shpilevoy 2019-06-15 9:52 ` Mergen Imeev 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 08/28] sql: remove SQL_PERM, SQL_WARNING, SQL_ABORT errcodes imeevma 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 09/28] sql: remove SQL_CANTOPEN errcode imeevma 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 10/28] sql: remove SQL_NOTFOUND error/status code imeevma 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 11/28] sql: remove SQL_LOCKED errcode imeevma 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 12/28] sql: remove SQL_FULL errcode imeevma 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 13/28] sql: remove SQL_MISUSE errcode imeevma 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 14/28] sql: remove SQL_RANGE errcode imeevma 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 15/28] sql: remove SQL_SCHEMA errcode imeevma 2019-06-13 22:24 ` [tarantool-patches] " Vladislav Shpilevoy 2019-06-15 9:55 ` Mergen Imeev 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 16/28] sql: remove SQL_TOOBIG errcode imeevma 2019-06-13 22:24 ` [tarantool-patches] " Vladislav Shpilevoy 2019-06-15 9:57 ` Mergen Imeev 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 17/28] sql: remove SQL_BUSY errcode imeevma 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 18/28] sql: remove SQL_CONSTRAINT errcode imeevma 2019-06-13 22:24 ` Vladislav Shpilevoy [this message] 2019-06-15 10:00 ` [tarantool-patches] " Mergen Imeev 2019-06-18 20:40 ` Vladislav Shpilevoy 2019-06-19 8:02 ` Mergen Imeev 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 19/28] sql: remove SQL_ERROR errcode imeevma 2019-06-10 13:56 ` [tarantool-patches] [PATCH v1 20/28] sql: remove SQL_NOMEM errcode imeevma 2019-06-13 22:24 ` [tarantool-patches] " Vladislav Shpilevoy 2019-06-15 10:01 ` Mergen Imeev 2019-06-10 13:57 ` [tarantool-patches] [PATCH v1 21/28] sql: remove SQL_IOERR errcode imeevma 2019-06-10 13:57 ` [tarantool-patches] [PATCH v1 22/28] sql: remove SQL_TARANTOOL_ERROR errcode imeevma 2019-06-10 13:57 ` [tarantool-patches] [PATCH v1 23/28] sql: remove field errMask from struct sql imeevma 2019-06-10 13:57 ` [tarantool-patches] [PATCH v1 24/28] sql: replace rc by is_aborted in struct VDBE imeevma 2019-06-10 13:57 ` [tarantool-patches] [PATCH v1 25/28] sql: remove sql_log() imeevma 2019-06-13 22:24 ` [tarantool-patches] " Vladislav Shpilevoy 2019-06-15 10:02 ` Mergen Imeev 2019-06-10 13:57 ` [tarantool-patches] [PATCH v1 26/28] sql: cleanup of legacy memory management system imeevma 2019-06-13 22:24 ` [tarantool-patches] " Vladislav Shpilevoy 2019-06-15 10:04 ` Mergen Imeev 2019-06-18 20:40 ` Vladislav Shpilevoy 2019-06-19 8:04 ` Mergen Imeev 2019-06-10 13:57 ` [tarantool-patches] [PATCH v1 27/28] sql: make function return void instead of int imeevma 2019-06-10 13:57 ` [tarantool-patches] [PATCH v1 28/28] sql: remove function sqlApiExit() imeevma 2019-06-11 10:00 ` [tarantool-patches] Re: [PATCH v1 00/28] sql: Remove SQL error system Imeev Mergen 2019-06-13 22:24 ` Vladislav Shpilevoy 2019-06-15 10:08 ` Mergen Imeev 2019-06-19 19:11 ` Vladislav Shpilevoy 2019-06-20 16:08 ` 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=a3433fb4-dbb9-1341-0485-d1365a1dab64@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=imeevma@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [PATCH v1 18/28] sql: remove SQL_CONSTRAINT errcode' \ /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