From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 4379922814 for ; Wed, 25 Jul 2018 17:06:01 -0400 (EDT) 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 SFeWme9h6zoS for ; Wed, 25 Jul 2018 17:06:01 -0400 (EDT) Received: from smtp5.mail.ru (smtp5.mail.ru [94.100.179.24]) (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 00EAC206E8 for ; Wed, 25 Jul 2018 17:06:00 -0400 (EDT) Subject: [tarantool-patches] Re: [PATCH v1 2/2] sql: prevent executing crossengine sql References: <281C2B94-5BA3-4868-B3A5-53234E2DCA4D@tarantool.org> From: Vladislav Shpilevoy Message-ID: <12091997-2a63-951d-9477-86c3429d981d@tarantool.org> Date: Thu, 26 Jul 2018 00:05:58 +0300 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format="flowed" Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-subscribe: List-owner: List-post: List-archive: To: tarantool-patches@freelists.org, Kirill Shcherbatov , Nikita Pettik Thanks for the patch! See 5 comments below. 1. Please, put a new patch version at the end of letter. > commit ae4310483bf126200f388be28a06b7580f3d9faa > Author: Kirill Shcherbatov > Date: Tue Jul 24 12:46:46 2018 +0300 > > sql: prevent executing cross-engine sql 2. crossengine looks like 'междудвижками'. Please, replace with cross-engine. > > Some sql requests are complex and could contain R/W with > multiple spaces. As we have no ability to make such changes > transactionaly, we have to dissallow such requests.> Since now iterators in SQL start transaction so we cant prevent > such vicious and dangeros things. 3. 'dissalow', 'dangeros' - no such words. > > Closes #3551 > > diff --git a/src/box/sql.c b/src/box/sql.c > index d48c3cfe5..a964fcbb1 100644 > --- a/src/box/sql.c > +++ b/src/box/sql.c > @@ -1118,12 +1118,23 @@ cursor_seek(BtCursor *pCur, int *pRes) > return SQL_TARANTOOL_ITERATOR_FAIL; > } > > + struct space *space = pCur->space; > + struct txn *txn = NULL; > + > + if (space->def->id != 0) { > + if (txn_begin_ro_stmt(space, &txn) != 0) > + return SQL_TARANTOOL_ERROR; > + } > struct iterator *it = index_create_iterator(pCur->index, pCur->iter_type, > key, part_count); > if (it == NULL) { > + if (txn != NULL) > + txn_rollback_stmt(); > pCur->eState = CURSOR_INVALID; > return SQL_TARANTOOL_ITERATOR_FAIL; > } > + if (txn != NULL) > + txn_commit_ro_stmt(txn); 4. Both commit_ro and rollback_ro already check for txn != NULL so please, remove the redundant checks. > pCur->iter = it; > pCur->eState = CURSOR_VALID; > > diff --git a/test/sql/triggers.result b/test/sql/triggers.result > index dc0a2e57d..a692b8945 100644 > --- a/test/sql/triggers.result > +++ b/test/sql/triggers.result > @@ -246,3 +246,123 @@ box.sql.execute("DROP VIEW V1;") > box.sql.execute("DROP TABLE T1;") > --- > ... > +-- > +-- gh-3531: Assertion with trigger and two storage engines > +-- > +-- Case 1: Src 'vinyl' table; Dst 'memtx' table > +box.sql.execute("PRAGMA sql_default_engine ('vinyl');") > +--- > +... > +box.sql.execute("CREATE TABLE m (s1 SCALAR PRIMARY KEY);") > +--- > +... > +box.sql.execute("CREATE TRIGGER m1 BEFORE UPDATE ON m FOR EACH ROW BEGIN UPDATE n SET s2 = DATETIME('now'); END;") > +--- > +... > +box.sql.execute("PRAGMA sql_default_engine('memtx');") > +--- > +... > +box.sql.execute("CREATE TABLE n (s1 CHAR PRIMARY KEY, s2 char);") > +--- > +... > +box.sql.execute("INSERT INTO m VALUES ('');") > +--- > +... > +box.sql.execute("INSERT INTO n VALUES ('',null);") > +--- > +... > +box.sql.execute("UPDATE m SET s1 = 'The Rain In Spain';") > +--- > +- error: A multi-statement transaction can not use multiple storage engines > +... > +-- ANALYZE operates with _sql_stat{1,4} tables should work > +box.sql.execute("ANALYZE m;") > +--- > +... > +box.sql.execute("DROP TABLE m;") > +--- > +... > +box.sql.execute("DROP TABLE n;") > +--- > +... > +-- Case 2: Src 'memtx' table; Dst 'vinyl' table > +box.sql.execute("PRAGMA sql_default_engine ('memtx');") > +--- > +... > +box.sql.execute("CREATE TABLE m (s1 SCALAR PRIMARY KEY);") > +--- > +... > +box.sql.execute("CREATE TRIGGER m1 BEFORE UPDATE ON m FOR EACH ROW BEGIN UPDATE n SET s2 = DATETIME('now'); END;") > +--- > +... > +box.sql.execute("PRAGMA sql_default_engine('vinyl');") > +--- > +... > +box.sql.execute("CREATE TABLE n (s1 CHAR PRIMARY KEY, s2 char);") > +--- > +... > +box.sql.execute("INSERT INTO m VALUES ('');") > +--- > +... > +box.sql.execute("INSERT INTO n VALUES ('',null);") > +--- > +... > +box.sql.execute("UPDATE m SET s1 = 'The Rain In Spain';") > +--- > +- error: A multi-statement transaction can not use multiple storage engines > +... > +-- ANALYZE operates with _sql_stat{1,4} tables should work > +box.sql.execute("ANALYZE n;") > +--- > +... > +box.sql.execute("DROP TABLE m;") > +--- > +... > +box.sql.execute("DROP TABLE n;") > +--- > +... > +-- Test SQL Transaction with LUA > +box.sql.execute("PRAGMA sql_default_engine ('memtx');") > +--- > +... > +box.sql.execute("CREATE TABLE test (id INT PRIMARY KEY)") > +--- > +... > +box.sql.execute("PRAGMA sql_default_engine='vinyl'") > +--- > +... > +box.sql.execute("CREATE TABLE test2 (id INT PRIMARY KEY)") > +--- > +... > +box.sql.execute("INSERT INTO test2 VALUES (2)") > +--- > +... > +test_run:cmd("setopt delimiter ';'") > +--- > +- true > +... > +function f() > + box.sql.execute("START TRANSACTION") > + box.sql.execute("INSERT INTO test VALUES (1)") > + box.sql.execute("SELECT * FROM test2") > + box.sql.execute("COMMIT") > +end; > +--- > +... > +f(); 5. Wit the same success you could inline f() and remove it. I gave this code to you into the function because I run it in the console. In test-run you anyway use "setopt delimiter" and can avoid this function enclosing. Or you even could put all this code in one line with no "setopt delimiter". There is no so many code. > +--- > +- error: A multi-statement transaction can not use multiple storage engines > +... > +box.sql.execute("ROLLBACK;"); > +--- > +... > +box.sql.execute("DROP TABLE test;"); > +--- > +... > +box.sql.execute("DROP TABLE test2;"); > +--- > +... > +test_run:cmd("setopt delimiter ''"); > +--- > +- true > +...