mariadb/mysql-test/suite/optimizer_unfixed_bugs/r/bug36981.result

set session debug_dbug="+d,optimizer_innodb_icp";
create table `t1` (`c1` char(1) default null,`c2` char(10) default null,
key (`c1`))
engine=innodb default charset=latin1;
insert into `t1` values ('3',null);
select * from `t1` where `c1`='3' for update;
c1	c2
3	NULL
drop table `t1`;
rename debug variable to debug_dbug, to make test pass in release builds (and to follow the naming conventons). keep old debug variable, but mark it as deprecated. 2011-12-15 22:07:58 +01:00			`set session debug_dbug="+d,optimizer_innodb_icp";`
Backport into MariaDB-5.2 the following: 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. 2009-12-15 10:16:46 +03:00			create table `t1` (`c1` char(1) default null,`c2` char(10) default null,
			key (`c1`))
			`engine=innodb default charset=latin1;`
			insert into `t1` values ('3',null);
			select * from `t1` where `c1`='3' for update;
			`c1 c2`
			`3 NULL`
			drop table `t1`;