MySQL Bugs: #37820: MyISAM and InnoDB provide different results on test with prefix index

Bug #37820	MyISAM and InnoDB provide different results on test with prefix index
Submitted:	2 Jul 2008 19:22	Modified:	3 Jul 2008 11:54
Reporter:	Zardosht Kasheff (OCA)	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Charsets	Severity:	S2 (Serious)
Version:	5.1.25-rc, 4.1, 5.0, 5.1, 6.0 bzr	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
This test was taken from the falcon test suite (falcon bug 29246) on MySQL alpha 6.0.3. I ran it on 5.1.25-rc
CREATE TABLE t1 (a varchar(2) CHARACTER SET latin1 COLLATE latin1_german2_ci);
INSERT INTO t1 VALUES (0xdc);
CREATE INDEX i1 ON t1 (a(1));
SELECT count(*) FROM t1 WHERE a = 'ue';
SELECT count(*) FROM t1;

The query that provides different results is "SELECT count(*) FROM t1 WHERE a = 'ue';"

Result for InnoDB:
SELECT count(*) FROM t1 WHERE a = 'ue';
count(*)
0

Result for MyISAM:
SELECT count(*) FROM t1 WHERE a = 'ue';
count(*)
1

According to the result file that came with the original test, MyISAM's result is correct.

How to repeat:
Run the test above.

Suggested fix:
The results should be the same.

Thank you for the report.

Verified as described.

Probably duplicate of either bug #29246 or bug #20447

Closed as duplicate of bug #29246

I see that the bug that this has been resolved to has a target version of 6.0. Does this mean the bug will not be fixed for 5.1 (I assume target version means what version the bug will be fixed for).

I've changed a target version of bug#29246