Browse Source
Bug #31221: Optimizer incorrectly identifies impossible WHERE clause
Bug #31221: Optimizer incorrectly identifies impossible WHERE clause
No warning was generated when a TIMESTAMP with a non-zero time part was converted to a DATE value. This caused index lookup to assume that this is a valid conversion and was returning rows that match a comparison between a TIMESTAMP value and a DATE keypart. Fixed by generating a warning on such a truncation.pull/73/head
13 changed files with 94 additions and 15 deletions
-
3mysql-test/r/derived.result
-
3mysql-test/r/ps_2myisam.result
-
3mysql-test/r/ps_3innodb.result
-
3mysql-test/r/ps_4heap.result
-
6mysql-test/r/ps_5merge.result
-
3mysql-test/r/ps_6bdb.result
-
3mysql-test/r/ps_7ndb.result
-
30mysql-test/r/type_date.result
-
2mysql-test/r/type_datetime.result
-
3mysql-test/t/derived.test
-
22mysql-test/t/type_date.test
-
25sql/field.cc
-
3sql/item_timefunc.cc
Write
Preview
Loading…
Cancel
Save
Reference in new issue