- 25 Jul, 2007 8 commits
-
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/inno/jul24/51
-
tsmith@ramayana.hindu.god authored
I forgot to check in some new files: lock0priv.h lock0priv.ic lock0iter.c lock0iter.h
-
iggy@amd64.(none) authored
into amd64.(none):/src/bug24732/my51-bug24732
-
iggy@amd64.(none) authored
- Required manual merge.
-
iggy@amd64.(none) authored
into amd64.(none):/src/bug24732/my51-bug24732
-
iggy@amd64.(none) authored
- Sign executables with MySQL AB security certificate.
-
tsmith@ramayana.hindu.god authored
Fixes: - Bug #23710: crash_commit_before fails if innodb_file_per_table=1 - Bug #28254: innodb crash if shutdown during innodb_table_monitor is running - Bug #28604: innodb_force_recovery restricts data dump - Bug #29097: fsp_get_available_space_in_free_extents() is capped at 4TB - Bug #29155: Innodb "Parallel recovery" is not prevented
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/jul24/51
-
- 24 Jul, 2007 2 commits
-
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/jul24/51
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/jul24/50
-
- 21 Jul, 2007 1 commit
-
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
- 20 Jul, 2007 18 commits
-
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/tmp3/mysql-5.0-build
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/tmp3/mysql-5.1-build
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/29898-bug-5.0-opt-mysql
-
joerg@trift-lap.none authored
into trift-lap.none:/MySQL/M51/push-5.1
-
joerg@trift-lap.none authored
into trift-lap.none:/MySQL/M50/push-5.0
-
joerg@trift-lap.none authored
into trift-lap.none:/MySQL/M51/push-5.1
-
-
ramil/ram@ramil.myoffice.izhnet.ru authored
into mysql.com:/home/ram/work/b28125/b28125.5.0
-
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.1-build
-
ramil/ram@ramil.myoffice.izhnet.ru authored
into mysql.com:/home/ram/work/b28125/b28125.5.1
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-
-
ramil/ram@ramil.myoffice.izhnet.ru authored
into mysql.com:/home/ram/work/b29923/b29923.5.1
-
Result adjusted.
-
ramil/ram@ramil.myoffice.izhnet.ru authored
into mysql.com:/home/ram/work/b28125/b28125.5.1
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
- 19 Jul, 2007 11 commits
-
-
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
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0.46
-
df@pippilotta.erinye.com authored
-
dkatz@damien-katzs-computer.local authored
into damien-katzs-computer.local:/Users/dkatz/51
-
evgen@moonbone.local authored
The Item_date_typecast::val_int function doesn't reset null_value flag. This makes all values that follows the first null value to be treated as nulls and led to a wrong result. Now the Item_date_typecast::val_int function correctly sets the null_value flag for both null and non-null values.
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-maint
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug26909/my51-bug26909
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint
-