[#MDEV-4061] LevelDB: Changes from an interrupted query are still applied

One connection starts a slow update, another connection kills the query in the first connection, the query ends with an error, but the changes are still applied.

Test output:

create table t1 (pk int primary key, a int) engine=LevelDB;

insert into t1 values (1,10),(2,20);

set autocommit = 1;

update t1 set a = sleep(10) where pk = 1;

connect  con1,localhost,root,,;

kill query 2;

connection default;

ERROR 70100: Query execution was interrupted

select * from t1;

pk      a

1       1

2       20

Test case:

--enable_connect_log

create table t1 (pk int primary key, a int) engine=LevelDB;

insert into t1 values (1,10),(2,20);

--let $con_id = `select connection_id()`

set autocommit = 1;

--send

update t1 set a = sleep(10) where pk = 1;

--connect (con1,localhost,root,,)

eval kill query $con_id;

--connection default

--error ER_QUERY_INTERRUPTED

--reap

select * from t1;

revision-id: psergey@askmonty.org-20130115181447-1jfr200qcuqzp1sr

revno: 4495

branch-nick: mysql-5.6-leveldb

LevelDB storage engine (MDEV-3841) [MDEV-4061] LevelDB: Changes from an interrupted query are still applied Created: 2013-01-16 Updated: 2013-05-02 Resolved: 2013-05-02
Status:	Closed
Project:	MariaDB Server
Component/s:	None
Affects Version/s:	None
Fix Version/s:	None

[MDEV-4061] LevelDB: Changes from an interrupted query are still applied Created: 2013-01-16 Updated: 2013-05-02 Resolved: 2013-05-02