- 28 Apr, 2007 1 commit
-
-
revert patch because these two test cases still fail on Solaris & Power BE machines
-
- 27 Apr, 2007 3 commits
-
-
into dev3-240.dev.cn.tlan:/home/justin.he/mysql/mysql-5.1/bug19710-5.1-new-ndb-bj
-
into dev3-240.dev.cn.tlan:/home/justin.he/mysql/mysql-5.1/bug19710-5.1-new-ndb-bj
-
into dev3-240.dev.cn.tlan:/home/justin.he/mysql/mysql-5.1/bug25431-5.1-new-ndb-bj
-
- 26 Apr, 2007 2 commits
-
-
gni@dev3-221.dev.cn.tlan authored
into dev3-221.dev.cn.tlan:/home/ngb/mysql/mysql-5.1/mysql-5.1-bug25741
-
lzhou/zhl@dev3-63.(none) authored
into dev3-63.(none):/home/zhl/mysql/mysql-5.1/bug27207
-
- 25 Apr, 2007 3 commits
-
-
lzhou/zhl@dev3-63.(none) authored
BUG#27207 Return correct error message when ndb_mgmd start with wrong config.ini parameter in TCP section
-
gni@dev3-221.dev.cn.tlan authored
-
add a new method is_equal in class Field_blob to compare BLOB field when alter table
-
- 24 Apr, 2007 5 commits
-
-
gni@dev3-221.dev.cn.tlan authored
into dev3-221.dev.cn.tlan:/home/ngb/mysql/mysql-5.1/bug18676
-
gni@dev3-221.dev.cn.tlan authored
into dev3-221.dev.cn.tlan:/home/ngb/mysql/mysql-5.1/bug18676
-
gni@dev3-221.dev.cn.tlan authored
into dev3-221.dev.cn.tlan:/home/ngb/mysql/mysql-5.1/mysql-5.1-bug22240
-
dli@dev3-164.dev.cn.tlan authored
into dev3-164.dev.cn.tlan:/home/dli/mysql/mysql-5.1/mysql-5.1-bug-23137
-
gni@dev3-221.dev.cn.tlan authored
BUG#22240 Upgrading from cluster 5.0 to 5.1 does not resize VARCHARS as expected. With --no-upgrade (-u) option, user can decide if ignore the upgrade, the default action is to upgrade them.
-
- 20 Apr, 2007 1 commit
-
-
lzhou/zhl@dev3-63.(none) authored
BUG#26675 remove additional varialbes definations in mysqld.cc and add NDBCLUSTER macro in set_var.cc
-
- 17 Apr, 2007 1 commit
-
-
lzhou/zhl@dev3-63.(none) authored
into dev3-63.(none):/home/zhl/mysql/mysql-5.1/bug26675
-
- 16 Apr, 2007 1 commit
-
-
gni/root@dev3-221.dev.cn.tlan authored
BUG#18676 In order to coincide with 5.0 mysqld error code after bug#18676, Map the 4009 ndb error code to 157 mysql error code
-
- 06 Apr, 2007 1 commit
-
-
update rpl_ndb_innodb2ndb and rpl_ndb_myisam2ndb testcase's option and result
-
- 05 Apr, 2007 9 commits
-
-
into dev3-240.dev.cn.tlan:/home/justin.he/mysql/mysql-5.1/mysql-5.1-new-ndb-bj.merge
-
mskold/marty@linux.site authored
into mysql.com:/windows/Linux_space/MySQL/mysql-5.1-new-ndb
-
mskold/marty@linux.site authored
into mysql.com:/windows/Linux_space/MySQL/mysql-5.1
-
mskold/marty@mysql.com/linux.site authored
-
mskold/marty@linux.site authored
into mysql.com:/windows/Linux_space/MySQL/mysql-5.1-new-ndb
-
mskold/marty@linux.site authored
into mysql.com:/windows/Linux_space/MySQL/mysql-5.1
-
mskold/marty@mysql.com/linux.site authored
-
into dev3-240.dev.cn.tlan:/home/justin.he/mysql/mysql-5.1/mysql-5.1-new-ndb-bj.merge
-
into dev3-240.dev.cn.tlan:/home/justin.he/mysql/mysql-5.1/mysql-5.1-new-ndb-bj.merge
-
- 04 Apr, 2007 12 commits
-
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user
-
kostja@vajra.(none) authored
-
mskold/marty@linux.site authored
into mysql.com:/windows/Linux_space/MySQL/mysql-5.1-new-ndb
-
mskold/marty@linux.site authored
into mysql.com:/windows/Linux_space/MySQL/mysql-5.1-new-ndb
-
mskold/marty@mysql.com/linux.site authored
-
tomas@whalegate.ndb.mysql.com authored
-
mskold/marty@linux.site authored
into mysql.com:/windows/Linux_space/MySQL/mysql-5.1-new-ndb
-
-
mskold/marty@linux.site authored
into mysql.com:/windows/Linux_space/MySQL/mysql-5.1
-
mskold/marty@mysql.com/linux.site authored
In certain cases AFTER UPDATE/DELETE triggers on NDB tables that referenced subject table didn't see the results of operation which caused invocation of those triggers. In other words AFTER trigger invoked as result of update (or deletion) of particular row saw version of this row before update (or deletion). The problem occured because NDB handler in those cases postponed actual update/delete operations to be able to perform them later as one batch. This fix solves the problem by disabling this optimization for particular operation if subject table has AFTER trigger for this operation defined. To achieve this we introduce two new flags for handler::extra() method: HA_EXTRA_DELETE_CANNOT_BATCH and HA_EXTRA_UPDATE_CANNOT_BATCH. These are called if there exists AFTER DELETE/UPDATE triggers during a statement that potentially can generate calls to delete_row()/update_row(). This includes multi_delete/multi_update statements as well as insert statements that do delete/update as part of an ON DUPLICATE statement.
-
gni/root@dev3-221.dev.cn.tlan authored
-
gni/root@dev3-221.dev.cn.tlan authored
into dev3-221.dev.cn.tlan:/home/ngb/mysql/mysql-5.1/bug18676
-
- 03 Apr, 2007 1 commit
-
-
kostja@bodhi.local authored
-