mirror of
https://github.com/MariaDB/server.git
synced 2025-02-01 03:21:53 +01:00
4747fa0c03
DATE and DATETIME can be compared either as strings or as int. Both methods have their disadvantages. Strings can contain valid DATETIME value but have insignificant zeros omitted thus became non-comparable with other DATETIME strings. The comparison as int usually will require conversion from the string representation and the automatic conversion in most cases is carried out in a wrong way thus producing wrong comparison result. Another problem occurs when one tries to compare DATE field with a DATETIME constant. The constant is converted to DATE losing its precision i.e. losing time part. This fix addresses the problems described above by adding a special DATE/DATETIME comparator. The comparator correctly converts DATE/DATETIME string values to int when it's necessary, adds zero time part (00:00:00) to DATE values to compare them correctly to DATETIME values. Due to correct conversion malformed DATETIME string values are correctly compared to other DATE/DATETIME values. As of this patch a DATE value equals to DATETIME value with zero time part. For example '2001-01-01' equals to '2001-01-01 00:00:00'. The compare_datetime() function is added to the Arg_comparator class. It implements the correct comparator for DATE/DATETIME values. Two supplementary functions called get_date_from_str() and get_datetime_value() are added. The first one extracts DATE/DATETIME value from a string and the second one retrieves the correct DATE/DATETIME value from an item. The new Arg_comparator::can_compare_as_dates() function is added and used to check whether two given items can be compared by the compare_datetime() comparator. Two caching variables were added to the Arg_comparator class to speedup the DATE/DATETIME comparison. One more store() method was added to the Item_cache_int class to cache int values. The new is_datetime() function was added to the Item class. It indicates whether the item returns a DATE/DATETIME value.
38 lines
820 B
Text
38 lines
820 B
Text
-- source include/not_embedded.inc
|
|
-- source include/have_bdb.inc
|
|
|
|
#
|
|
# Bug #16206: Superfluous COMMIT event in binlog when updating BDB in autocommit mode
|
|
#
|
|
set autocommit=1;
|
|
|
|
let $VERSION=`select version()`;
|
|
|
|
reset master;
|
|
create table bug16206 (a int);
|
|
insert into bug16206 values(1);
|
|
start transaction;
|
|
insert into bug16206 values(2);
|
|
commit;
|
|
--replace_result $VERSION VERSION
|
|
--replace_column 1 f 2 n 5 n
|
|
show binlog events;
|
|
drop table bug16206;
|
|
|
|
reset master;
|
|
create table bug16206 (a int) engine= bdb;
|
|
insert into bug16206 values(0);
|
|
insert into bug16206 values(1);
|
|
start transaction;
|
|
insert into bug16206 values(2);
|
|
commit;
|
|
insert into bug16206 values(3);
|
|
--replace_result $VERSION VERSION
|
|
--replace_column 1 f 2 n 5 n
|
|
show binlog events;
|
|
drop table bug16206;
|
|
|
|
set autocommit=0;
|
|
|
|
|
|
--echo End of 5.0 tests
|