1. 14 Feb, 2007 12 commits
    • unknown's avatar
      Merge willster.(none):/home/stewart/Documents/MySQL/5.0/ndb-work · b0aba1f9
      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
      b0aba1f9
    • unknown's avatar
      BUG#26358 remove unused and non-working SET_VAR_REQ/CONF signals · 6f334b55
      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)
      6f334b55
    • unknown's avatar
      BUG#26357 remove unused GSN_STATISTICS_REQ and CONF · f8a679e9
      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
      f8a679e9
    • unknown's avatar
      BUG#26356 uninitialised data sent from TAMPER_ORD to DIHNDBTAMPER · cea0d57d
      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.
      cea0d57d
    • unknown's avatar
      BUG#26355 FIXME: use constant for max loglevel in ndb_mgmd · e953dd8a
      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
      e953dd8a
    • unknown's avatar
      BUG#26353 remove GET_CONFIG_BACKWARDS_COMPAT from ndb_mgmd · a031b430
      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
      a031b430
    • unknown's avatar
      BUG#26352 unused ndb_mgm_rep_command in mgmapi.cpp · 22d157e4
      unknown authored
      
      ndb/src/mgmapi/mgmapi.cpp:
        remove ndb_mgm_rep_command function
      22d157e4
    • unknown's avatar
      Merge tulin@bk-internal.mysql.com:/home/bk/mysql-5.0 · 94679180
      unknown authored
      into  poseidon.mysql.com:/home/tomas/mysql-5.0-ndb
      
      
      94679180
    • unknown's avatar
      WL#3704 mgmapi timeouts (and cleanups) · 7fd6bbce
      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)
      7fd6bbce
    • unknown's avatar
      Merge poseidon.mysql.com:/home/tomas/mysql-5.0-telco-gca · b6876ef6
      unknown authored
      into  poseidon.mysql.com:/home/tomas/mysql-5.0-ndb
      
      
      b6876ef6
    • unknown's avatar
    • unknown's avatar
      Bug#26293 cluster mgmt node sometimes doesn't receive events from all nodes on restart · 9ed1b843
      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
      9ed1b843
  2. 13 Feb, 2007 2 commits
  3. 12 Feb, 2007 4 commits
    • unknown's avatar
      Merge tnurnberg@bk-internal.mysql.com:/home/bk/mysql-5.0-maint · 1c285489
      unknown authored
      into  mysql.com:/home/tnurnberg/24660/50-24660
      
      
      sql/table.cc:
        Auto merged
      sql/unireg.cc:
        Auto merged
      1c285489
    • unknown's avatar
      Merge tnurnberg@bk-internal.mysql.com:/home/bk/mysql-4.1-maint · 8a34c4bb
      unknown authored
      into  mysql.com:/home/tnurnberg/24660/41-24660
      
      
      sql/table.cc:
        Auto merged
      8a34c4bb
    • unknown's avatar
      Merge mysql.com:/home/tnurnberg/24660/41-24660 · 91f684a5
      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
      91f684a5
    • unknown's avatar
      Bug#24660: "enum" field type definition problem · 4dc7c1aa
      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.
      4dc7c1aa
  4. 09 Feb, 2007 2 commits
  5. 08 Feb, 2007 3 commits
  6. 07 Feb, 2007 8 commits
  7. 06 Feb, 2007 9 commits