From 9dca45c0e37bd581d20f988c964bdd8a7e3d10a3 Mon Sep 17 00:00:00 2001 From: unknown Date: Mon, 20 Jun 2005 08:56:37 +0000 Subject: Fix for BUG#8441: in index_merge code when creating index search tuples use KEY_PART_INFO::store_length, not KEY_PART_INFO::length (like range code does) mysql-test/r/index_merge_innodb.result: Testcase for BUG8441 mysql-test/t/index_merge_innodb.test: Testcase for BUG8441 --- mysql-test/t/index_merge_innodb.test | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'mysql-test/t/index_merge_innodb.test') diff --git a/mysql-test/t/index_merge_innodb.test b/mysql-test/t/index_merge_innodb.test index 5e270c161a2..c10ce3b9688 100644 --- a/mysql-test/t/index_merge_innodb.test +++ b/mysql-test/t/index_merge_innodb.test @@ -120,3 +120,14 @@ select count(*) from t1 where drop table t1,t2; +# Test for BUG#8441 +create table t1 ( + id1 int, + id2 date , + index idx2 (id1,id2), + index idx1 (id2) +) engine = innodb; +insert into t1 values(1,'20040101'), (2,'20040102'); +select * from t1 where id1 = 1 and id2= '20040101'; +drop table t1; + -- cgit v1.2.1