- 26 Apr, 2006 16 commits
-
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-5.1-bug18129
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-5.1-bug18129
-
mskold@mysql.com authored
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-5.1-ss492
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-5.1-ss492
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-5.1-ss492
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-5.0-ss492-work
-
aivanov@mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-5.1-ss492-work
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-5.0-ss492-work
-
aivanov@mysql.com authored
Use files innodb_mysql.[test|result] instead.
-
aivanov@mysql.com authored
* Fix BUG#19217 "dict_load_indexes() may read the delete-mark incorrectly". * Remove obsolete and unused variables from srv0srv.c. * Remove srv_sys->operational since it is unused. * Make thread_id parameter in os_thread_create() optional. * Add platform-specific os_thread_ret_t and OS_THREAD_DUMMY_RETURN, and convert thread start functions to use them.
-
andrey@lmy004. authored
some platforms.
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-5.1-ss492-work Null-merge.
-
aivanov@mysql.com authored
Fixed BUG#19217 "dict_load_indexes() may read the delete-mark incorrectly".
-
- 25 Apr, 2006 24 commits
-
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new
-
tomas@poseidon.ndb.mysql.com authored
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.1-new
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.1-new
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new
-
andrey@lmy004. authored
into lmy004.:/work/mysql-5.1-new-clean
-
aelkin@mysql.com authored
the fix from 5.0 with necessary modifications applied.
-
aelkin@mysql.com authored
into mysql.com:/home/elkin/MySQL/MERGE/5.1-new
-
stewart@mysql.com authored
small cleanup fixes in kernel/vm/Configuration
-
pem@mysql.com authored
-
jonas@perch.ndb.mysql.com authored
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb
-
jonas@perch.ndb.mysql.com authored
Fix bootstrap/compile error
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb
-
tomas@poseidon.ndb.mysql.com authored
-
ingo@mysql.com authored
into mysql.com:/home/mydev/mysql-5.1-bug18129
-
pem@mysql.com authored
into mysql.com:/extern/mysql/5.1/generic/mysql-5.1-new
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/50-work
-
jonas@perch.ndb.mysql.com authored
Handle early abort of scan, so that resources are correctly freed
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new
-
tomas@poseidon.ndb.mysql.com authored
- the replica info was not stored in byte order indepentent format - backup/restore still compatible 5.0->5.1 - but patch makes previous 5.1 versions completely incompatible
-
jonas@perch.ndb.mysql.com authored
1) relax version check for restore block since no changes has happend since 5.1.6 and improve error message on check failure 2) improve lcp/backup max write size...
-