1. 14 Feb, 2005 11 commits
  2. 13 Feb, 2005 2 commits
    • unknown's avatar
      row0mysql.c: · 602d9a03
      unknown authored
        Fix memory corruption bug reported by Georg Richter: if one created a table whose primary key contained at least 2 column prefixes, that could corrupt the memory heap of prebuilt_t
      
      
      innobase/row/row0mysql.c:
        Fix memory corruption bug reported by Georg Richter: if one created a table whose primary key contained at least 2 column prefixes, that could corrupt the memory heap of prebuilt_t
      602d9a03
    • unknown's avatar
      Merge mysql.com:/Users/kent/mysql/bk/mysql-4.1-perl · f37290b9
      unknown authored
      into mysql.com:/Users/kent/mysql/bk/mysql-5.0-compile
      
      
      f37290b9
  3. 12 Feb, 2005 2 commits
  4. 11 Feb, 2005 13 commits
  5. 10 Feb, 2005 12 commits
    • unknown's avatar
      Merge commit trigger · a20374e3
      unknown authored
      
      BitKeeper/etc/logging_ok:
        auto-union
      extra/replace.c:
        Auto merged
      BitKeeper/triggers/post-commit:
        Merge changes
      a20374e3
    • unknown's avatar
      Merge bk-internal:/home/bk/mysql-4.0 · 77d24615
      unknown authored
      into mysql.com:/home/jimw/my/mysql-4.0-clean
      
      
      77d24615
    • unknown's avatar
    • unknown's avatar
      BUG#6749: If there is no current database, then nothing should be binlogged if · 9f4f7980
      unknown authored
      binlog-do-db or binlog-ignore-db are in effect.   (In the future 5.1? 5.0? I think 
      each statement should be verified against the filtering criteria based on the database
      it *uses* and not the *current* one.  But, right now the *current* database is what 
      counts according to the semantics of the manual.)
      
      
      sql/log.cc:
        BUG#6749: If there is no current database, then nothing should be binlogged if
        binlog-do-db or binlog-ignore-db are in effect.   (In the future I think that each 
        statement should be verified against the filtering criteria based on the database
        it *uses* and not the *current* one.  But, right now the *current* database is what 
        counts according to the semantics of the manual.)
      9f4f7980
    • unknown's avatar
      Merge three.local.lan:/home/matthias/Arbeit/mysql-5.0/src · 9fe4e2a4
      unknown authored
      into three.local.lan:/home/matthias/Arbeit/mysql-5.0/src-WL1420
      
      
      9fe4e2a4
    • unknown's avatar
      Merge mysql.com:/home/bkroot/mysql-5.0 · 6520c161
      unknown authored
      into mysql.com:/home/bk/b7853-mysql-5.0
      
      
      client/mysqlbinlog.cc:
        Auto merged
      mysql-test/r/mysqlbinlog.result:
        Auto merged
      6520c161
    • unknown's avatar
      Bug#8391 - "merge" fails on Linux/IA64 · 8abafe35
      unknown authored
      It was a thread stack overrun.
      IA64 had its own stack size section already.
      Enlarged its default stack size from 192K to 256K.
      
      
      8abafe35
    • unknown's avatar
      Merge mysql.com:/home/kostja/work/mysql-4.1-root · 6cdda5b3
      unknown authored
      into mysql.com:/home/kostja/work/mysql-5.0-root
      
      
      libmysql/libmysql.c:
        Auto merged
      tests/mysql_client_test.c:
        Auto merged
      6cdda5b3
    • unknown's avatar
      Follow-up for bug#7990 · d9039e87
      unknown authored
      
      libmysql/libmysql.c:
        And now put it to the proper place and make it work (Bug#7990)
      tests/mysql_client_test.c:
        Enable the test for bug#7990
      d9039e87
    • unknown's avatar
      Merge mysql.com:/home/kostja/work/mysql-4.1-root · 98bc2348
      unknown authored
      into mysql.com:/home/kostja/work/mysql-5.0-root
      
      
      libmysql/libmysql.c:
        Auto merged
      tests/mysql_client_test.c:
        Auto merged
      98bc2348
    • unknown's avatar
      Fix -ansi -pedantic compilation failure. · bebba958
      unknown authored
      bebba958
    • unknown's avatar
      A fix and test case for Bug#7990 "mysql_stmt_close doesn't · a26ce94f
      unknown authored
      reset mysql->net.last_error": the solution is to clear
      MYSQL->net error before performing COM_CLOSE: if the call
      succeeds, the connection is usable for other statements.
      More comprehensive fix is to clear MYSQL->net for all
      recoverable errors at the time they happen, it will be
      implemented in 5.0 as it introduces incompatibility in behavior.
      
      
      libmysql/libmysql.c:
        A simple fix for Bug#7990 "mysql_stmt_close doesn't reset 
        mysql->net.last_error"
      tests/mysql_client_test.c:
        A test case for Bug#7990 " mysql_stmt_close doesn't reset 
        mysql->net.last_error"
      a26ce94f