LevelDB storage engine (MDEV-3841)

[MDEV-4054] LevelDB: Reading by PK prefix does not work (fails with "Table storage engine doesn't have this option") Created: 2013-01-15  Updated: 2013-01-23  Resolved: 2013-01-23

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

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

Issue Links:
Relates

 Description   

Test output:

create table t1 (i int, j int, k int, primary key(i,j,k)) engine=LevelDB;
insert into t1 values (1,10,100),(2,20,200);
select * from t1 where i = 1;
ERROR HY000: Table storage engine for 't1' doesn't have this option
select * from t1 where j = 10;
i       j       k
1       10      100
select * from t1 where k = 100;
i       j       k
1       10      100
select * from t1 where i = 1 and j = 10;
ERROR HY000: Table storage engine for 't1' doesn't have this option
select * from t1 where i = 1 and k = 100;
ERROR HY000: Table storage engine for 't1' doesn't have this option
select * from t1 where j = 10 and k = 100;
i       j       k
1       10      100
select * from t1 where i = 1 and j = 10 and k = 100;
i       j       k
1       10      100

Test case:

--disable_abort_on_error
 
create table t1 (i int, j int, k int, primary key(i,j,k)) engine=LevelDB;
insert into t1 values (1,10,100),(2,20,200);
select * from t1 where i = 1;
select * from t1 where j = 10;
select * from t1 where k = 100;
select * from t1 where i = 1 and j = 10;
select * from t1 where i = 1 and k = 100;
select * from t1 where j = 10 and k = 100;
select * from t1 where i = 1 and j = 10 and k = 100;

revision-id: psergey@askmonty.org-20130115181447-1jfr200qcuqzp1sr
revno: 4495
branch-nick: mysql-5.6-leveldb



 Comments   
Comment by Sergei Petrunia [ 2013-01-17 ]

Will be fixed when adding support for range scanning.

Comment by Sergei Petrunia [ 2013-01-23 ]

Fixed after the latest changes. Test case added to leveldb.test.

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