LevelDB storage engine (MDEV-3841)

[MDEV-4035] LevelDB: SELECT produces different results inside a transaction (read is not repeatable) Created: 2013-01-14  Updated: 2013-01-14  Resolved: 2013-01-14

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Technical task Priority: Major
Reporter: Elena Stepanova Assignee: Sergei Petrunia
Resolution: Fixed Votes: 0
Labels: leveldb

Issue Links:
Relates

 Description   

Test case:

--enable_connect_log
 
 
 
create table t1 (pk int primary key, i int) engine=LevelDB;
 
begin;
 
select * from t1;
 
select * from t1 where pk = 1;
 
 
 
--connect (con1,localhost,root,,)
 
insert into t1 values (1,100);
 
 
 
--connection default
 
select * from t1;
 
select * from t1 where pk = 1;
 
commit;
 
 

Output:

create table t1 (pk int primary key, i int) engine=LevelDB;
 
begin;
 
select * from t1;
 
pk      i
 
select * from t1 where pk = 1;
 
pk      i
 
connect  con1,localhost,root,,;
 
insert into t1 values (1,100);
 
connection default;
 
select * from t1;
 
pk      i
 
1       100
 
select * from t1 where pk = 1;
 
pk      i
 
commit;

With InnoDB the same test case works as expected (all SELECTs return an empty result set).

revision-id: psergey@askmonty.org-20130114131529-qv3531bw9fdklwob
 
revno: 4483
 
branch-nick: mysql-5.6-leveldb


Generated at Thu Feb 08 06:53:13 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.