- 22 Oct, 2007 4 commits
-
-
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/my51-30638
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/29801/my51-29801
-
- 21 Oct, 2007 6 commits
-
-
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 9 commits
-
-
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
-
tnurnberg@sin.intern.azundris.com authored
into sin.intern.azundris.com:/misc/mysql/31588/50-31588
-
tnurnberg@sin.intern.azundris.com authored
Buffer used when setting variables was not dimensioned to accomodate trailing '\0'. An overflow by one character was therefore possible. CS corrects limits to prevent such overflows.
-
- 17 Oct, 2007 4 commits
-
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B27099-5.1-opt
-
gluh@mysql.com/eagle.(none) authored
move 'table_collation' field filling outside of if(file) condition because this field has 'OPEN_FRM_ONLY' attribute
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@mysql.com/eagle.(none) authored
updated result files
-
- 16 Oct, 2007 2 commits
-
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-
- 15 Oct, 2007 5 commits
-
-
gkodinov/kgeorge@magare.gmz authored
On Windows the debug log was doing freopen () instead of fflush() and that was slowing the logging down that much that some tests timed out. Fixed by replacing the freopen() with an syncing-to-disk flag to fopen() and fflush(). Also increased the timeout of the tests running with --debug on windows : seems to slow down as much as valgrind on linux.
-
gluh@mysql.com/eagle.(none) authored
issue an error if string has illegal characters
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
holyfoot/hf@mysql.com/hfmain.(none) authored
if remote server sends malicious response. We need to check if the SHOW TABLE STATUS query we issue inside the FEDERATED engine returned the result with the proper (or just sufficient) number of rows. Otherwise statements like row[12] can crash the server.
-
- 14 Oct, 2007 2 commits
-
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B31156-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
Fixed dbug macros usage errors
-
- 13 Oct, 2007 4 commits
-
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/B31156-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B31156-5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B31440-5.1-opt
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B31440-5.0-opt
-
- 12 Oct, 2007 1 commit
-
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-