- 14 Feb, 2007 12 commits
-
-
unknown authored
into willster.(none):/home/stewart/Documents/MySQL/5.0/ndb-merge ndb/src/kernel/blocks/dbdih/DbdihMain.cpp: Auto merged ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp: SCCS merged
-
unknown authored
remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/include/kernel/GlobalSignalNumbers.h: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/common/debugger/signaldata/SignalNames.cpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/cmvmi/Cmvmi.hpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/dbacc/Dbacc.hpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/dbacc/DbaccInit.cpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/dbacc/DbaccMain.cpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/dbdih/Dbdih.hpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/dbdih/DbdihInit.cpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/dbdih/DbdihMain.cpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/dblqh/Dblqh.hpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/dblqh/DblqhInit.cpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/dblqh/DblqhMain.cpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/dbtc/Dbtc.hpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/dbtc/DbtcInit.cpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/dbtc/DbtcMain.cpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/dbtup/Dbtup.hpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/dbtup/DbtupGen.cpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/ndbcntr/Ndbcntr.hpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/ndbcntr/NdbcntrInit.cpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/ndbcntr/NdbcntrMain.cpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/qmgr/Qmgr.hpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/qmgr/QmgrInit.cpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/kernel/blocks/qmgr/QmgrMain.cpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers) ndb/src/mgmsrv/MgmtSrvr.hpp: remove SET_VAR_REQ,REF,CONF - unused, #if 0 and confusing Remove the dead SET_VAR_REQ,REF,CONF signals. They: a) don't currently work b) will cause confusion with future mgmd updates for signal interface to configuration things (e.g. port numbers)
-
unknown authored
remove GSN_STATISTICS_REQ and CONF These are unused and have been since BK import. not needed. ndb/include/kernel/GlobalSignalNumbers.h: remove STATISTICS_REQ and CONF ndb/src/common/debugger/signaldata/SignalNames.cpp: remove signal names for STATISTICS_REQ and CONF (unused) ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp: remove unused STATISTICS signals ndb/src/kernel/blocks/cmvmi/Cmvmi.hpp: remove unused STATISTICS signals
-
unknown authored
Don't send uninit data in TAMPER_ORD to DIHNDBTAMPER Even though this data is unused from the CMVMI (mgmd) signal, we shouldn't be doing stuff with uninited data. ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp: init the 3rd word of DIHNDBTAMPER before sending to DIH.
-
unknown authored
ndb/include/mgmapi/mgmapi.h: use constant for max log level in ndb_mgmd. (more useful in 5.1 due to other defines and refinements of mgmapi) ndb/src/mgmsrv/Services.cpp: fix the XXX fixme of constant for max log level
-
unknown authored
there is backwards compatibility for GET CONFIG style configuration requests in ndb_mgmd. None of the ndbd versions that use this couldn't possibly connect to a 5.0 or 5.1 cluster. remove the backwards compat remove it ndb/src/mgmsrv/Services.cpp: remove MGM_GET_CONFIG_BACKWARDS_COMPAT code. any client using GET CONFIG will just not work with modern NDB. ndb/src/mgmsrv/Services.hpp: remove GET CONFIG support
-
unknown authored
ndb/src/mgmapi/mgmapi.cpp: remove ndb_mgm_rep_command function
-
unknown authored
into poseidon.mysql.com:/home/tomas/mysql-5.0-ndb
-
unknown authored
indicate units in SocketOutputStream timeout rename timeout in SocketOutputStream to reflect units (ms) In 5.0 as well as is safe cleanup patch that will help with merging. ndb/include/util/OutputStream.hpp: rename timeout in SocketOutputStream to reflect units (ms) ndb/src/common/util/OutputStream.cpp: rename timeout in SocketOutputStream to reflect units (ms)
-
unknown authored
into poseidon.mysql.com:/home/tomas/mysql-5.0-ndb
-
unknown authored
-
unknown authored
- signals where sometimes sent too early when setting up subscriptions ndb/include/kernel/signaldata/DumpStateOrd.hpp: added dump for active subscriptions in cmvmi ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp: added dump for active subscriptions in cmvmi ndb/src/mgmsrv/MgmtSrvr.cpp: bug in that signals where sent prior to api reg conf arrived, causing thrown away signals and subsequent hangs in mgmtserver also add retry if node connected but not yet received api reg conf ndb/src/ndbapi/ClusterMgr.cpp: added status variable m_api_reg_conf in cluster manager to correctly be able to determine if a node is sendable ndb/src/ndbapi/ClusterMgr.hpp: added status variable m_api_reg_conf in cluster manager to correctly be able to determine if a node is sendable ndb/src/ndbapi/SignalSender.cpp: assert to see that node is sendable when signal is sent ndb/src/ndbapi/SignalSender.hpp: manke metchd const
-
- 13 Feb, 2007 2 commits
-
-
unknown authored
into pilot.mysql.com:/home/msvensson/mysql/mysql-5.0-maint BitKeeper/etc/ignore: auto-union
-
unknown authored
into pilot.mysql.com:/home/msvensson/mysql/mysql-5.0-maint BitKeeper/etc/gone: auto-union mysys/my_getopt.c: Auto merged sql/sql_prepare.cc: Auto merged sql/table.cc: Auto merged
-
- 12 Feb, 2007 4 commits
-
-
unknown authored
into mysql.com:/home/tnurnberg/24660/50-24660 sql/table.cc: Auto merged sql/unireg.cc: Auto merged
-
unknown authored
into mysql.com:/home/tnurnberg/24660/41-24660 sql/table.cc: Auto merged
-
unknown authored
into mysql.com:/home/tnurnberg/24660/50-24660 mysql-test/r/type_enum.result: Auto merged sql/table.cc: Auto merged sql/unireg.cc: Auto merged
-
unknown authored
ENUMs weren't allowed to have character 0xff, a perfectly good character in some locales. This was circumvented by mapping 0xff in ENUMs to ',', thereby prevent actual commas from being used. Now if 0xff makes an appearance, we find a character not used in the enum and use that as a separator. If no such character exists, we throw an error. Any solution would have broken some sort of existing behaviour. This solution should serve both fractions (those with 0xff and those with ',' in their enums), but WILL REQUIRE A DUMP/RESTORE CYCLE FROM THOSE WITH 0xff IN THEIR ENUMS. :-/ That is, mysqldump with their current server, and restore when upgrading to one with this patch. mysql-test/r/type_enum.result: Bug#24660: "enum" field type definition problem Show that enums can now contain NAMES_SEP_CHAR (0xff, which is a perfectly respectable char in some locales), or ',', or both. mysql-test/t/type_enum.test: Bug#24660: "enum" field type definition problem Show that enums can now contain NAMES_SEP_CHAR (0xff, which is a perfectly respectable char in some locales), or ',', or both. sql/table.cc: Bug#24660: "enum" field type definition problem Revert fix for Bug#20922. sql/unireg.cc: Bug#24660: "enum" field type definition problem Use a field-separator for ENUM-values that is not part of those values. If impossible, throw error.
-
- 09 Feb, 2007 2 commits
- 08 Feb, 2007 3 commits
-
-
unknown authored
Copy "ndb_size.tmpl" into binary distribution (Bug#24191) scripts/make_binary_distribution.sh: Copy "ndb_size.tmpl" into binary distribution (Bug#24191)
-
unknown authored
into siva.hindu.god:/home/tsmith/m/bk/maint/50
-
unknown authored
into siva.hindu.god:/home/tsmith/m/bk/maint/41 sql/sql_prepare.cc: Manual merge
-
- 07 Feb, 2007 8 commits
-
-
unknown authored
into poseidon.mysql.com:/home/tomas/mysql-4.1-ndb
-
unknown authored
into poseidon.mysql.com:/home/tomas/mysql-5.0-ndb sql/ha_ndbcluster.cc: Auto merged
-
unknown authored
Avoid problem with "noinst_HEADERS" being sucked into "mysqld_LDADD" if openssl_libs and yassl_libs are empty strings
-
unknown authored
into trift2.:/MySQL/M50/push-5.0
-
unknown authored
into mysql.com:/windows/Linux_space/MySQL/mysql-5.0-ndb
-
unknown authored
into mysql.com:/windows/Linux_space/MySQL/mysql-5.0-ndb ndb/include/ndbapi/NdbIndexScanOperation.hpp: Auto merged ndb/include/ndbapi/NdbScanOperation.hpp: Auto merged ndb/src/ndbapi/NdbScanOperation.cpp: Auto merged sql/ha_ndbcluster.cc: Auto merged sql/ha_ndbcluster.h: Auto merged
-
unknown authored
bug#25821 Excessive partition pruning for multi-range index scan in NDB API: added multi_range error checking in end_of_bound ha_ndbcluster.h: Removed stray mthod declaration sql/ha_ndbcluster.h: Removed stray mthod declaration ndb/include/ndbapi/NdbScanOperation.hpp: bug#25821 Excessive partition pruning for multi-range index scan in NDB API: added multi_range error checking in end_of_bound ndb/src/ndbapi/NdbScanOperation.cpp: bug#25821 Excessive partition pruning for multi-range index scan in NDB API: added multi_range error checking in end_of_bound sql/ha_ndbcluster.cc: bug#25821 Excessive partition pruning for multi-range index scan in NDB API: added multi_range error checking in end_of_bound
-
unknown authored
bug#25821 Excessive partition pruning for multi-range index scan in NDB API: post-review fix, added default value
-
- 06 Feb, 2007 9 commits
-
-
unknown authored
Fix for bug#25821 Excessive partition pruning for multi-range index scan in NDB API: don't set distribution key if multi_range
-
unknown authored
into pilot.mysql.com:/home/msvensson/mysql/mysql-5.0-maint extra/perror.c: Auto merged
-
unknown authored
into pilot.mysql.com:/home/msvensson/mysql/mysql-4.1-maint
-
unknown authored
- strerror might return NULL on some platforms extra/perror.c: Backport fix from 5.0
-
unknown authored
into pilot.mysql.com:/home/msvensson/mysql/mysql-5.0-maint vio/vio.c: Auto merged vio/viossl.c: Auto merged
-
unknown authored
into pilot.mysql.com:/home/msvensson/mysql/mysql-5.0-maint
-
unknown authored
BitKeeper/etc/ignore: Added mysql-test/mysql-test-run-shell to the ignore list mysql-test/suite/funcs_2/include/check_charset.inc: finished files with newline
-
unknown authored
into pilot.mysql.com:/home/msvensson/mysql/mysql-5.0-maint vio/viosslfactories.c: Auto merged
-
unknown authored
- Send output from 'ERR_print_errors_fp' to DBUG_FILE if --debug is used vio/viosslfactories.c: Send output from 'ERR_print_errors_fp' to DBUG_FILE if --debug is used
-