diff options
| author | unknown <ramil/ram@mysql.com/ramil.myoffice.izhnet.ru> | 2007-11-21 08:01:00 +0400 |
|---|---|---|
| committer | unknown <ramil/ram@mysql.com/ramil.myoffice.izhnet.ru> | 2007-11-21 08:01:00 +0400 |
| commit | f2a631f0dcd87d6d53ae0293bfb70364ca30dc4d (patch) | |
| tree | cd48c8b1187ac8681709e99b0a327f08c93e7009 /mysql-test/lib/mtr_io.pl | |
| parent | caa031e0f76c769f044d39c4f244c8fbee71c3f0 (diff) | |
| download | mariadb-git-f2a631f0dcd87d6d53ae0293bfb70364ca30dc4d.tar.gz | |
Fix for bug #32021: Using Date 000-00-01 in WHERE causes wrong result
Problem: caching 00000000-00000099 dates as integer values we're
improperly shifting them up twice in the get_datetime_value().
Fix: don't shift cached DATETIME values up for the second time.
mysql-test/r/type_date.result:
Fix for bug #32021: Using Date 000-00-01 in WHERE causes wrong result
- test result.
mysql-test/t/type_date.test:
Fix for bug #32021: Using Date 000-00-01 in WHERE causes wrong result
- test case.
sql/item.h:
Fix for bug #32021: Using Date 000-00-01 in WHERE causes wrong result
- Item_cache::field_type() method added.
- new Item_cache(enum_field_types) and Item_cache_int(enum_field_types)
constructors added.
sql/item_cmpfunc.cc:
Fix for bug #32021: Using Date 000-00-01 in WHERE causes wrong result
- don't shift cached DATETIME values for the second time in the
get_datetime_value():
creating new Item_cache_int set DATETIME filed type,
check the type before shifting.
Diffstat (limited to 'mysql-test/lib/mtr_io.pl')
0 files changed, 0 insertions, 0 deletions