- 24 Apr, 2007 8 commits
-
-
msvensson@pilot.blaudden authored
into pilot.blaudden:/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@pilot.blaudden authored
into pilot.blaudden:/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@pilot.blaudden authored
into pilot.blaudden:/home/msvensson/mysql/mysql-5.0-maint
-
into mysql.com:/home/ram/work/b27515/b27515.5.0
-
-
into mysql.com:/home/ram/work/b27515/b27515.5.0
-
iggy@recycle.(none) authored
into recycle.(none):/src/bug24732/my50-bug24732
-
iggy@recycle.(none) authored
- Correct PushBuild failure.
-
- 23 Apr, 2007 17 commits
-
-
iggy@recycle.(none) authored
into recycle.(none):/src/bug24732/my50-bug24732
-
iggy@recycle.(none) authored
- Added script to generate application specific manifest. - Added new CMake MACRO to add customer build events which will first generate a manifest and then embeds that manifest into an executable.
-
tsmith@quadxeon.mysql.com authored
Fix minor merge "oopsie"
-
iggy@recycle.(none) authored
into recycle.(none):/src/bug25621/my50-bug25621
-
iggy@recycle.(none) authored
- On Windows, connection handlers while exiting properly did not decrement the server's thread count.
-
msvensson@pilot.blaudden authored
-
msvensson@pilot.blaudden authored
into pilot.blaudden:/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@pilot.blaudden authored
Fix "make distcheck"
-
msvensson@pilot.blaudden authored
so the WEXITSTATUS macro can "fiddle" with it as it so pleases
-
msvensson@pilot.blaudden authored
to check if the creation of mysql_upgrade_info suceeded. Instead use 'upgrade_already_done' to check that file was created properly.
-
msvensson@pilot.blaudden authored
-
msvensson@pilot.blaudden authored
into pilot.blaudden:/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@pilot.blaudden authored
-
msvensson@pilot.blaudden authored
-
msvensson@pilot.blaudden authored
-
msvensson@pilot.blaudden authored
into pilot.blaudden:/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@pilot.blaudden authored
-
- 21 Apr, 2007 1 commit
-
-
mjorgensen@blade09.mysql.com authored
into blade09.mysql.com:/tmp/mmj/mysql-5.0-runtime
-
- 20 Apr, 2007 14 commits
-
-
ibabaev@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.0-opt
-
malff/marcsql@weblab.(none) authored
into weblab.(none):/home/marcsql/TREE/mysql-5.0-rt-merge
-
mtaylor@qualinost.(none) authored
into qualinost.(none):/home/mtaylor/src/mysql/mysql-5.0-debian
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint
-
cmiller@zippy.cornsilk.net authored
-
mats@romeo.(none) authored
-
gshchepa/uchum@gshchepa.loc authored
into gshchepa.loc:/home/uchum/work/bk-trees/mysql-5.0-opt-27704
-
gshchepa/uchum@gshchepa.loc authored
into gshchepa.loc:/home/uchum/work/bk-trees/mysql-5.0-opt-27704
-
gshchepa/uchum@gshchepa.loc authored
Support for NULL components was incomplete for row comparison, fixed. Added support for abort_on_null at compare_row() like in 5.x
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B27786-5.0-opt
-
mhansson@dl145s.mysql.com authored
This bug was intruduced by the fix for bug#17212 (in 4.1). It is not ok to call test_if_skip_sort_order since this function will alter the execution plan. By contract it is not ok to call test_if_skip_sort_order in this context. This bug appears only in the case when the optimizer has chosen an index for accessing a particular table but finds a covering index that enables it to skip ORDER BY. This happens in test_if_skip_sort_order.
-
mats@romeo.(none) authored
into romeo.(none):/home/bk/merge-mysql-5.0
-
mats@romeo.(none) authored
into romeo.(none):/home/bkroot/mysql-5.0-rpl
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-maint
-