mirror of
https://github.com/MariaDB/server.git
synced 2025-01-31 11:01:52 +01:00
96e092dc73
WL#2474 "Multi Range Read: Change the default MRR implementation to implement new MRR interface"
WL#2475 "Batched range read functions for MyISAM/InnoDb"
"Index condition pushdown for MyISAM/InnoDB"
Igor's fix from sp1r-igor@olga.mysql.com-20080330055902-07614:
There could be observed the following problems:
1. EXPLAIN did not mention pushdown conditions from on expressions in the
'extra' column. As a result if a query had no where conditions pushed
down to a table, but had on conditions pushed to this table the 'extra'
column in the EXPLAIN for the table missed 'using where'.
2. Conditions for ref access were not eliminated from on expressions
though such conditions were eliminated from the where condition.
17 lines
557 B
Text
17 lines
557 B
Text
# Test for BUG#43249 "Innodb returns zero time for the time column
|
|
# with <=> NULL order by limit"
|
|
|
|
--source include/have_debug.inc
|
|
--source include/have_innodb.inc
|
|
|
|
set session debug="+d,optimizer_innodb_icp";
|
|
|
|
CREATE TABLE t1(c1 TIME NOT NULL, c2 TIME NULL, c3 DATE, PRIMARY
|
|
KEY(c1), UNIQUE INDEX(c2)) engine=innodb;
|
|
INSERT INTO t1 VALUES('8:29:45',NULL,'2009-02-01');
|
|
# first time, good results:
|
|
SELECT * FROM t1 WHERE c2 <=> NULL ORDER BY c2 LIMIT 2;
|
|
# second time, bad results:
|
|
SELECT * FROM t1 WHERE c2 <=> NULL ORDER BY c2 LIMIT 2;
|
|
|
|
drop table `t1`;
|