Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
Description
The following test case gives us a wrong result in MariaDB 5.2/5.5
CREATE TABLE t1 (
c1 VARCHAR(10) NOT NULL,
KEY i1 (c1(3))
) ENGINE=MEMORY DEFAULT CHARSET=latin1;
INSERT INTO t1 VALUES ('foo1'), ('bar2'), ('baz3');
SELECT * FROM t1 WHERE c1='bar2';
MariaDB [test]> SELECT * FROM t1 WHERE c1='bar2';
Empty set (0.00 sec)
(see also bug #47704 from bugs.mysql.com)
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Re: Wrong result for a lookup query from a heap table
This is a problem with hash indexes. I will look into fixing this.
It works if you add 'using btree' to the KEY il