An error occurred fetching the project authors.
- 07 Jul, 2006 1 commit
-
-
unknown authored
Disable test cases ndb_alter_table3, ndb_autodiscover3, ndb_dd_advance, and ndb_multi in statement-based binlogging mode until bug can be fixed. mysql-test/t/ndb_alter_table3.test: Disable test in statement-based binlogging mode. mysql-test/t/ndb_autodiscover3.test: Disable test in statement-based binlogging mode. mysql-test/t/ndb_dd_advance.test: Disable test in statement-based binlogging mode. mysql-test/t/ndb_multi.test: Disable test in statement-based binlogging mode.
-
- 18 May, 2006 1 commit
-
-
unknown authored
Bug #17610 ndbapi: dropEventOperation leaves object behind, memleak mysql-test/r/ndb_autodiscover3.result: Bug #19395 mysqld does not always detect cluster shutdown mysql-test/t/disabled.def: Bug #19395 mysqld does not always detect cluster shutdown mysql-test/t/ndb_autodiscover3.test: Bug #19395 mysqld does not always detect cluster shutdown sql/ha_ndbcluster_binlog.cc: Bug #19395 mysqld does not always detect cluster shutdown storage/ndb/include/ndbapi/Ndb.hpp: Bug #19395 mysqld does not always detect cluster shutdown storage/ndb/include/ndbapi/NdbDictionary.hpp: Bug #17610 ndbapi: dropEventOperation leaves object behind, memleak storage/ndb/src/kernel/blocks/suma/Suma.cpp: Bug #17610 ndbapi: dropEventOperation leaves object behind, memleak storage/ndb/src/ndbapi/Ndb.cpp: Bug #19395 mysqld does not always detect cluster shutdown storage/ndb/src/ndbapi/NdbEventOperationImpl.cpp: Bug #17610 ndbapi: dropEventOperation leaves object behind, memleak storage/ndb/src/ndbapi/NdbEventOperationImpl.hpp: Bug #17610 ndbapi: dropEventOperation leaves object behind, memleak
-
- 17 May, 2006 1 commit
-
-
unknown authored
sql/ha_ndbcluster_binlog.cc: Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail - small correction of previous patch storage/ndb/src/ndbapi/DictCache.cpp: Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail - cache not released properly storage/ndb/tools/desc.cpp: Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail - added retry option so that ndb_desc can be used to wait for a table to be created
-
- 16 May, 2006 1 commit
-
-
unknown authored
- adoptions to handle binlog
-
- 15 May, 2006 1 commit
-
-
unknown authored
- invalidate ndb dict cache on cluster disconnect (ClusterMgr.cpp) - add check for correct frm on external lock when table cache is found invalid ndb/include/ndbapi/ndb_cluster_connection.hpp: Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail ndb/src/ndbapi/ClusterMgr.cpp: Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail ndb/src/ndbapi/ClusterMgr.hpp: Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail ndb/src/ndbapi/DictCache.cpp: Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail ndb/src/ndbapi/DictCache.hpp: Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail ndb/src/ndbapi/TransporterFacade.hpp: Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail ndb/src/ndbapi/ndb_cluster_connection.cpp: Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail ndb/src/ndbapi/ndb_cluster_connection_impl.hpp: Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail sql/ha_ndbcluster.cc: Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail mysql-test/r/ndb_autodiscover3.result: Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail mysql-test/t/ndb_autodiscover3.test: Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail
-