- 15 Jul, 2007 1 commit
-
-
evgen@moonbone.local authored
The get_time_value function is added. It is used to obtain TIME values both from items the can return time as an integer and from items that can return time only as a string. The Arg_comparator::compare_datetime function now uses pointer to a getter function to obtain values to compare. Now this function is also used for comparison of TIME values. The get_value_func variable is added to the Arg_comparator class. It points to a getter function for the DATE/DATETIME/TIME comparator.
-
- 14 Jul, 2007 5 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/29729-bug-5.0-opt-mysql
-
evgen@moonbone.local authored
The Field_newdate::store when storing a DATETIME value was returning the 'value was cut' error even if the thd->count_cuted_fields flag is set to CHECK_FIELD_IGNORE. This made range optimizr think that there is no appropriate data in the table and thus to return an empty set. Now the Field_newdate::store function returns conversion error only if the thd->count_cuted_fields flag isn't set to CHECK_FIELD_IGNORE.
-
sergefp@mysql.com authored
-
sergefp@pylon64.mylan authored
into mysql.com:/home/psergey/mysql-5.0-bug29740
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-merge
-
- 13 Jul, 2007 4 commits
-
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
sergefp@mysql.com authored
- return HA_KEY_SCAN_NOT_ROR flag for HASH indexes; - Fix ha_heap::cmp_ref() to work with BTREE index scans.
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
-
- 12 Jul, 2007 4 commits
-
-
evgen@moonbone.local authored
Time values were compared by the BETWEEN function as strings. This led to a wrong result in cases when some of arguments are less than 100 hours and other are greater. Now if all 3 arguments of the BETWEEN function are of the TIME type then they are compared as integers.
-
gkodinov/kgeorge@magare.gmz authored
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug29604
-
igor@olga.mysql.com authored
A bug in the restore_prev_nj_state function allowed interleaving inner tables of outer join operations with outer tables. With the current implementation of the nested loops algorithm it could lead to wrong result sets for queries with nested outer joins. Another bug in this procedure effectively blocked evaluation of some valid execution plans for queries with nested outer joins.
-
- 11 Jul, 2007 11 commits
-
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt-29360
-
gshchepa/uchum@gleb.loc authored
Additional fix for bug #29360.
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/29555-bug-5.0-opt-mysql
-
evgen@moonbone.local authored
Time values were compared as strings. This led to a wrong comparison result when comparing values one of which is under 100 hours and another is over 100 hours. Now when the Arg_comparator::set_cmp_func function sees that both items to compare are of the TIME type it sets the comparator to the Arg_comparator::compare_e_int or the Arg_comparator::compare_int_unsigned functions.
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
gshchepa/uchum@gleb.loc authored
The special `zero' enum value was coerced to the normal empty string enum value during a field-to-field copy. This bug affected CREATE ... SELECT statements and SELECT aggregate GROUP BY enum field statements. Also this bug made unnecessary warnings during the execution of CREATE ... SELECT statements: Warning 1265 Data truncated for column...
-
gkodinov/kgeorge@magare.gmz authored
test if TRUNCATE TABLE works with keep_files_on_create
-
gkodinov/kgeorge@magare.gmz authored
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B29325-5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
By default MyISAM overwrites .MYD and .MYI files no DATA DIRECTORY option is used. This can lead to two tables using the same .MYD and .MYI files (that can't be dropped). To prevent CREATE TABLE from overwriting a file a new option is introduced : keep_files_on_create When this is on the CREATE TABLE throws an error if either the .MYD or .MYI exists for a MyISAM table. The option is off by default (resulting in compatible behavior).
-
- 10 Jul, 2007 3 commits
-
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B29070-5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
The Ctrl-C handler in mysql closes the console while ReadConsole() waits for console input. But the main thread was detecting that ReadConsole() haven't read anything and was processing as if there're data in the buffer. Fixed to handle correctly this error condition. No test case added as the test relies on Ctrl-C sent to the client from its console.
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B29070-5.0-opt
-
- 09 Jul, 2007 11 commits
-
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
tsmith@sita.local authored
Backport from 5.1 a fix to make this test deterministic
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
gkodinov/kgeorge@magare.gmz authored
1. Threat MBR for a key as double[] and convert it only when about to store it on disk. 2. Remove the redundant function get_double().
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-maint
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/41
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
ramil/ram@ramil.myoffice.izhnet.ru authored
into mysql.com:/home/ram/work/b28808/b28808.5.0
-
tsmith@sita.local authored
into sita.local:/Users/tsmith/m/bk/maint/50
-
- 08 Jul, 2007 1 commit
-
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/29461-bug-5.0-opt-mysql
-