LevelDB storage engine (MDEV-3841)

[MDEV-4084] LevelDB: Wrong result on IN subquery with index lookup Created: 2013-01-24  Updated: 2013-01-25  Resolved: 2013-01-25

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   

CREATE TABLE t1 (pk INT PRIMARY KEY, a INT, KEY(a)) ENGINE=LevelDB;
INSERT INTO t1 VALUES (1,10),(2,20);
 
EXPLAIN EXTENDED
SELECT 3 IN ( SELECT a FROM t1 );
id	select_type	table	type	possible_keys	key	key_len	ref	rows	filtered	Extra
1	PRIMARY	NULL	NULL	NULL	NULL	NULL	NULL	NULL	NULL	No tables used
2	DEPENDENT SUBQUERY	t1	index_subquery	a	a	5	const	20	100.00	Using index
Warnings:
Note	1003	/* select#1 */ select <in_optimizer>(3,<exists>(<index_lookup>(<cache>(3) in t1 on a checking NULL having <is_not_null_test>(`test`.`t1`.`a`)))) AS `3 IN ( SELECT a FROM t1 )`
 
SELECT 3 IN ( SELECT a FROM t1 );
3 IN ( SELECT a FROM t1 )
1

Test case:

CREATE TABLE t1 (pk INT PRIMARY KEY, a INT, KEY(a)) ENGINE=LevelDB;
INSERT INTO t1 VALUES (1,10),(2,20);
 
SELECT 3 IN ( SELECT a FROM t1 );

revision-id: psergey@askmonty.org-20130124165745-nm4yaxrsu8e4o2ll
revno: 4511
branch-nick: mysql-5.6-leveldb


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