1. 25 Nov, 2004 7 commits
    • unknown's avatar
      table.cc: · 26339663
      unknown authored
        Bug #6802 MySQL 4.0's VARCHAR(NN) BINARY is interpreted as VARBINARY(NN) in 4.1
      
      
      sql/table.cc:
        Bug #6802 MySQL 4.0's VARCHAR(NN) BINARY is interpreted as VARBINARY(NN) in 4.1
      26339663
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.1/ · 9fc190e6
      unknown authored
      into serg.mylan:/usr/home/serg/Abk/mysql-4.1
      
      
      9fc190e6
    • unknown's avatar
      Merge tulin@bk-internal.mysql.com:/home/bk/mysql-4.1 · 897b7cbd
      unknown authored
      into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-clean
      
      
      897b7cbd
    • unknown's avatar
      ndb/src/common/logger/LogHandler.cpp · 45f941cb
      unknown authored
          changed so that error is returned if format is wrong in logger param parsing
      ndb/src/common/logger/Logger.cpp
          some debuf printout added
      ndb/src/mgmsrv/InitConfigFileParser.cpp
          rewrote parsing on parseNameValuePair, was buggy
      
      
      ndb/src/common/logger/LogHandler.cpp:
        changed so that error is returned if format is wrong in logger param parsing
      ndb/src/common/logger/Logger.cpp:
        some debuf printout added
      ndb/src/mgmsrv/InitConfigFileParser.cpp:
        rewrote parsing on parseNameValuePair, was buggy
      45f941cb
    • unknown's avatar
      Merge joreland@bk-internal.mysql.com:/home/bk/mysql-4.1 · 32c3009d
      unknown authored
      into mysql.com:/home/jonas/src/mysql-4.1
      
      
      32c3009d
    • unknown's avatar
      Merge mysql.com:/home/jonas/src/mysql-4.1-fix · 0e6d4fd0
      unknown authored
      into mysql.com:/home/jonas/src/mysql-4.1
      
      
      ndb/src/kernel/blocks/dblqh/DblqhMain.cpp:
        Auto merged
      0e6d4fd0
    • unknown's avatar
      bug#6775 - ndb - fix bug introduced by bug fix · 5aaffe9b
      unknown authored
      
      ndb/src/kernel/blocks/dblqh/DblqhMain.cpp:
        Scan number allocation must be on table even in case of range scan
        Otherwise scan takeover won't work as LQHKEYREQ contains table
      5aaffe9b
  2. 24 Nov, 2004 27 commits
  3. 23 Nov, 2004 6 commits