- 12 Oct, 2007 5 commits
-
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/31155/my51-31155
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/31155/my51-31155
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/31155/my50-31155
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/31155/my51-31155
-
- 11 Oct, 2007 4 commits
-
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
gluh@mysql.com/eagle.(none) authored
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@mysql.com/eagle.(none) authored
Bug#30982 CHAR(..USING..) can return a not-well-formed string Bug#30986 Character set introducer followed by a HEX string can return bad result check_well_formed_result moved to Item from Item_str_func fixed Item_func_char::val_str for proper ucs symbols converting added check for well formed strings for correct conversion of constants with underscore charset
-
- 10 Oct, 2007 8 commits
-
-
gshchepa/uchum@gleb.loc authored
precision > 0 && scale <= precision'. A sign of a resulting item of the IFNULL function was not updated and the maximal length of this result was calculated improperly. Correct algorithm was copy&pasted from the IF function implementation.
-
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.1-opt
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-
gluh@mysql.com/eagle.(none) authored
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@mysql.com/eagle.(none) authored
added variables relay_log, relay_log_index, relay_log_info_file to init_vars[] to make them visible within SHOW VARIABLES
-
gluh@mysql.com/eagle.(none) authored
removed now() call to make the test to be year independent
-
- 09 Oct, 2007 11 commits
-
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/bug31160/my51-bug31160
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/bug31160/my51-bug31160
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/bug31160/my50-bug31160
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/bug31160/my50-bug31160
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug31160/my51-bug31160
-
mhansson/martin@linux-st28.site authored
Even though it returns NULL, the MAKETIME function did not have this property set, causing a failed assertion (designed to catch exactly this). Fixed by setting the nullability property of MAKETIME().
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug30832-again-push/my51-bug30832-again
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug30832-again-push/my50-bug30832-again
-
mhansson/martin@linux-st28.site authored
into linux-st28.site:/home/martin/mysql/src/bug30832-again/my51-bug30832-again
-
mhansson/martin@linux-st28.site authored
Completion of previous patch. Negative number were denied as the second argument to NAME_CONST.
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/bug30942/my51-bug30942
-
- 08 Oct, 2007 2 commits
-
-
gshchepa/uchum@gleb.loc authored
Locked rows of the InnoDB storage was silently skipped in the read-committed isolation level. QUICK_RANGE_SELECT for unique ranges lacks second (blocking) read of the record that was read semi-consistently and just skip it. The handler::read_multi_range_next method has been modified to retry previous unique range if the previous read was semi-consistent.
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/bug30942/my51-bug30942
-
- 06 Oct, 2007 1 commit
-
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B31094-5.1-opt
-
- 05 Oct, 2007 9 commits
-
-
gkodinov/kgeorge@magare.gmz authored
A rule was introduced by the 5.1 part of the fix for bug 27531 to prefer filesort over indexed ORDER BY when accessing all of the rows of a table (because it's faster). This new rule was not accounting for the presence of a LIMIT clause. Fixed the condition for this rule so it will prefer filesort over indexed ORDER BY only if no LIMIT.
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30286/my51-30286
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30286/my50-30286
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/bug30942/my51-bug30942
-
mhansson@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/mhansson/bug30942/my50-bug30942
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30286/my51-30286
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30286/my50-30286
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/home/hf/work/30286/my41-30286
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30286/my51-30286
-