- 04 Apr, 2007 1 commit
-
-
did not run properly on a fast Windows machine
-
- 03 Apr, 2007 2 commits
-
-
svoj@june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG25729/mysql-5.1-engines
-
svoj@mysql.com/june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG25729/mysql-5.0-engines
-
- 02 Apr, 2007 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
LEFT JOIN Fixed that in certain situations MATCH ... AGAINST returns false hits for NULLs produced by LEFT JOIN when there is no fulltext index available.
-
- 31 Mar, 2007 3 commits
-
-
svoj@mysql.com/april.(none) authored
-
svoj@april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG26138/mysql-5.1-engines
-
svoj@mysql.com/june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG26138/mysql-5.0-engines
-
- 30 Mar, 2007 8 commits
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.1-axmrg
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.1-axmrg
-
tomas@whalegate.ndb.mysql.com authored
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-axmrg
-
svoj@mysql.com/june.mysql.com authored
ARCHIVE table ARCHIVE table was truncated by REPAIR TABLE ... USE_FRM statement. The table handler returned its file name extensions in a wrong order. REPAIR TABLE believed it has to use the meta file to create a new table from it. With the fixed order, REPAIR TABLE does now use the data file to create a new table. So REPAIR TABLE ... USE_FRM works well with ARCHIVE engine now. This issue affects 5.0 only, since in 5.1 ARCHIVE engine stores meta information and data in the same file.
-
istruewing@chilla.local authored
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.1-axmrg
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.1-axmrg
-
- 29 Mar, 2007 18 commits
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.1-axmrg
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.0-axmrg
-
svoj@april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG25521/mysql-5.1-engines
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/BUG25521/mysql-5.0-engines
-
tomas@whalegate.ndb.mysql.com authored
- do not try to perge binlog when purge comes from slave, it never purges binlog anyways
-
istruewing@chilla.local authored
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-ndb
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user
-
tomas@whalegate.ndb.mysql.com authored
- quick workaround, better patch is needed later - test case
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user
-
tomas@whalegate.ndb.mysql.com authored
- also run this patch on 32 bit machines to allow online upgrade
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user
-
tomas@whalegate.ndb.mysql.com authored
- increase var part reference from 32 to 64 bits on 64 bit systems - note current patch does not allow for online upgrade from 32 to 64 bit systems or vice versa
-
joerg@trift-lap.fambruehe authored
into trift-lap.fambruehe:/MySQL/M51/push-5.1
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-5.1-axmrg
-
- 28 Mar, 2007 7 commits
-
-
kent@mysql.com/kent-amd64.(none) authored
Extended test section Removed duplicate EXTRA_DIST
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/tmp/mysql-5.1-build
-
kent@mysql.com/kent-amd64.(none) authored
Don't install ndb man pages if no ndb configured config-win.h, CMakeLists.txt, README, configure.js: Removed Cybozu patches
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/tmp/mysql-5.1-build
-
baker@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.1-arch
-
joerg@trift-lap.fambruehe authored
-
svoj@mysql.com/april.(none) authored
losing it's .MYD When OPTIMIZE TABLE is completed it attempts to rename temporary file to original name. This step may fail on windows when a file is opened. As a result data file might be deleted and optimized copy of file (table_name.MYD) remains. This situation is handled properly by my_delete_allow_opened, so use it instead of my_delete when attempting to rename a file on windows. No suitable test case for this bug.
-