- 23 Oct, 2007 14 commits
-
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30638/my51-30638
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B30825-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30638/my51-30638
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B28687-5.1-opt
-
holyfoot/hf@mysql.com/hfmain.(none) authored
-
holyfoot/hf@mysql.com/hfmain.(none) authored
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30638/my51-30638
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30638/my51-30638
-
holyfoot/hf@mysql.com/hfmain.(none) authored
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/B30825-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B30825-new-5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/B28687-5.1-opt
-
gluh@mysql.com/eagle.(none) authored
added correct handling of NULL values for lookup fields
-
- 22 Oct, 2007 8 commits
-
-
gkodinov/kgeorge@magare.gmz authored
When doing indexed search the server constructs a key image for faster comparison to the stored keys. While doing that it must not perform (and stop if they fail) the additional date checks that can be turned on by the SQL mode because there already may be values in the table that don't comply with the error checks. Fixed by ignoring these SQL mode bits while making the key image.
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30638/my51-30638
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30638/my51-30638
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30638/my50-30638
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30638/my50-30638
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30638/my51-30638
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30638/my51-30638
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/29801/my51-29801
-
- 21 Oct, 2007 7 commits
-
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/scratch/tnurnberg/31588/50-31588
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/scratch/tnurnberg/31588/51-31588
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/mysql-5.1-opt
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/mysql-5.1-opt
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/mysql-5.0-opt
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/bug28550/my51-bug28550
-
kaa@polly.(none) authored
Since, as of MySQL 5.0.15, CHAR() arguments larger than 255 are converted into multiple result bytes, a single CHAR() argument can now take up to 4 bytes. This patch fixes Item_func_char::fix_length_and_dec() to take this into account. This patch also fixes a regression introduced by the patch for bug21513. As now we do not always have the 'name' member of Item set for Item_hex_string and Item_bin_string, an own print() method has been added to Item_hex_string so that it could correctly be printed by Item_func::print_args().
-
- 20 Oct, 2007 1 commit
-
-
tnurnberg@sin.intern.azundris.com authored
into sin.intern.azundris.com:/misc/mysql/31588/51-31588
-
- 19 Oct, 2007 2 commits
-
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B31157-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
The uncacheable flag should be set at fix_fields() stage. Fixed by moving the flag setting to match the one in 5.1
-
- 18 Oct, 2007 8 commits
-
-
tnurnberg@white.intern.koehntopp.de authored
into mysql.com:/scratch/tnurnberg/31588/50-31588
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/B31221-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/B31221-5.0-gca-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B31221-5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
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.
-
holyfoot/hf@mysql.com/hfmain.(none) authored
The BIG_TABLES define wasn't enabled on Windows. #define added
-
tnurnberg@sin.intern.azundris.com authored
post-merge fixes: format string was changed 5.0 -> 5.1, resulting in longer output
-
tnurnberg@sin.intern.azundris.com authored
into sin.intern.azundris.com:/misc/mysql/31588/51-31588
-