mariadb/mysql-test/r/cache_temporal_4265.result

create table t1 (a date);
insert t1 values ('2000-01-02'), ('2001-02-03'), ('2002-03-04');
set debug_dbug='d,str_to_datetime_warn';
select * from t1 where a > date_add('2000-01-01', interval 5 day);
a
2001-02-03
2002-03-04
Warnings:
Note	1003	2000-01-01
drop table t1;
MDEV-4265 5.5 is slower than 5.3 because of many str_to_datetime calls get_datetime_value() should not double-cache its own Item_cache_temporal items, but it should cache other Item_cache items, such as Item_cache_str. sql/item.h: shortcut, to avoid going through the switch in Item::cmp_type() sql/item_cmpfunc.cc: even if the item is Item_cache_str - it still needs to be converted and cached. sql/item_timefunc.h: all descendants of Item_temporal_func always have cmp_type==TIME_RESULT. Even Item_date_add_interval, that might have field_type == MYSQL_TYPE_STRING. 2013-03-13 22:33:52 +01:00			`create table t1 (a date);`
			`insert t1 values ('2000-01-02'), ('2001-02-03'), ('2002-03-04');`
			`set debug_dbug='d,str_to_datetime_warn';`
			`select * from t1 where a > date_add('2000-01-01', interval 5 day);`
			`a`
			`2001-02-03`
			`2002-03-04`
			`Warnings:`
			`Note 1003 2000-01-01`
			`drop table t1;`