- 23 Jan, 2008 3 commits
-
-
mskold/marty@quadfish.(none) authored
into mysql.com:/home/marty/MySQL/mysql-5.1-new-ndb
-
Changed function attribute names to match implementation
-
Add a check if setting an auto_increment field will change it's next value before retrieving tuple_id_range lock. This avoids hitting locks when updating auto_increment values to a lower value than the current maximum. This is useful in loading a table with auto_increment where one loads the highest numbered pk's first and then proceeds backwards to the first. This can then be achieved with the same performance as a normal insert without auto_increment. ndb_restore.result: Updated result file
-
- 22 Jan, 2008 3 commits
-
-
-
into mysql.com:/home/marty/MySQL/mysql-5.1-new-ndb
-
Add new variable m_highest_seen when only peeking at auto_increment NEXTID and not retrieving to cache. Add new method to check tupleId before calling data node ndb_restore.result, ndb_restore.test: Changed test to use information_schema to check auto_increment DictCache.cpp, Ndb.cpp: Add new variable m_highest_seen when only peeking at auto_increment NEXTID and not retrieving to cache. Add new method to check tupleId before calling data node. When setting the auto_increment value we'll also read up the new value, this is useful if we use the table the first time in this MySQL Server and haven't yet seen the NEXTID value. The kernel will avoid updating since it already has the value but will also read up the NEXTID value to ensure we don't need to do this any more time. ndb_auto_increment.result: Updated result file since it was incorrect
-
- 11 Dec, 2007 4 commits
-
-
mskold/marty@quadfish.(none) authored
into mysql.com:/home/marty/MySQL/mysql-5.1-new-ndb
-
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/cge-5.1
-
tomas@whalegate.ndb.mysql.com authored
-
- 10 Dec, 2007 7 commits
-
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb-merge
-
tomas@whalegate.ndb.mysql.com authored
(bug not present in 5.1)
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb-merge
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb-merge
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-ndb-merge
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb-merge
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-ndb-merge
-
- 07 Dec, 2007 18 commits
-
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51
-
tsmith@ramayana.hindu.god authored
-
-
mskold/marty@quadfish.(none) authored
into mysql.com:/home/marty/MySQL/mysql-5.1-new-ndb
-
-
mskold/marty@quadfish.(none) authored
into mysql.com:/home/marty/MySQL/mysql-5.1-new-ndb
-
-
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/50
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51-merge
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/50
-
tsmith@ramayana.hindu.god authored
-
-
mskold/marty@quadfish.(none) authored
into mysql.com:/home/marty/MySQL/mysql-5.1-new-ndb
-
-
tsmith@ramayana.hindu.god authored
testing embedded server works correctly.
-
- 06 Dec, 2007 3 commits
-
-
tsmith@ramayana.hindu.god authored
-
tsmith@ramayana.hindu.god authored
-
bug#21072 Duplicate key error in NDB references wrong key: Return correct key for non-batching inserts
-
- 05 Dec, 2007 2 commits
-
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51-merge
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/50
-