1. 25 Nov, 2004 2 commits
    • unknown's avatar
      Merge mysql.com:/space/bkroot/mysql-4.0 · 99ef45cb
      unknown authored
      into mysql.com:/space/bk/b6148-mysql-4.0
      
      
      BitKeeper/etc/logging_ok:
        Logging to logging@openlogging.org accepted
      99ef45cb
    • unknown's avatar
      Fix for Bug#6148. Only rewind read position in binary log when the · 324b3a45
      unknown authored
      slave SQL thread is started.
      
      
      sql/slave.cc:
        Adding threads to init as parameter to init_master_info.
        Only rewind read position when starting SQL thread.
      sql/slave.h:
        Adding threads to init as parameter to init_master_info.
        Only rewind read position when starting SQL thread.
      sql/sql_repl.cc:
        Adding threads to init as parameter to init_master_info.
        Only rewind read position when starting SQL thread.
      sql/repl_failsafe.cc:
        Adding threads to init as parameter to init_master_info.
        Only rewind read position when starting SQL thread.
      324b3a45
  2. 24 Nov, 2004 1 commit
  3. 23 Nov, 2004 1 commit
    • unknown's avatar
      Change "Do-compile" to make automatic build log analysis easier and · b03daf97
      unknown authored
      to run the standard tests with "--force" (default, can be switched off).
      
      
      Build-tools/Do-compile:
        1) For an automated log analysis, we need a clear marker in the build log
           whether compile + link succeeded: Write it after successful "make".
        2) Ensure the standard tests are run with "--force" in the default case,
           but allow the old behaviour by an option "--one-error".
        3) Correct a typing error in the usage message.
      b03daf97
  4. 22 Nov, 2004 4 commits
  5. 19 Nov, 2004 1 commit
  6. 18 Nov, 2004 1 commit
  7. 17 Nov, 2004 1 commit
  8. 16 Nov, 2004 1 commit
    • unknown's avatar
      ha_innodb.cc: · 305a9468
      unknown authored
        Fix InnoDB bug #6287: if one uses INSERT IGNORE to insert several rows at a time, and the first inserts are ignored because of a duplicate key collision, then InnoDB in a replication slave assigns AUTO_INCREMENT values 1 bigger than in the master
      
      
      sql/ha_innodb.cc:
        Fix InnoDB bug #6287: if one uses INSERT IGNORE to insert several rows at a time, and the first inserts are ignored because of a duplicate key collision, then InnoDB in a replication slave assigns AUTO_INCREMENT values 1 bigger than in the master
      305a9468
  9. 15 Nov, 2004 1 commit
    • unknown's avatar
      Proposed fix for bug #6439 "from_unixtime() function returns wrong datetime · c4134b7a
      unknown authored
      values for too big argument".
      
      Added range checking for from_unixtime() argument, cleaned up code 
      a bit.
      
      
      mysql-test/r/func_time.result:
        Test for bug #6439 "from_unixtime() function returns wrong datetime 
        values for too big argument".
      mysql-test/t/func_time.test:
        Test for bug #6439 "from_unixtime() function returns wrong datetime 
        values for too big argument".
      sql/item_timefunc.cc:
        Item_func_from_unixtime: 
          Added error range checking for function argument + small code clean up.
      c4134b7a
  10. 12 Nov, 2004 4 commits
  11. 11 Nov, 2004 4 commits
  12. 10 Nov, 2004 3 commits
    • unknown's avatar
      Merge paul@bk-internal.mysql.com:/home/bk/mysql-4.0 · 1d9de021
      unknown authored
      into kite-hub.kitebird.com:/src/extern/MySQL/bk/mysql-4.0
      
      1d9de021
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · 50b36f46
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      50b36f46
    • unknown's avatar
      Fix for BUG#6522 "Replication fails due to a rolled back transaction in the binlog" · 38c6f97d
      unknown authored
      When we are writing a transaction to the binlog, we log BEGIN/COMMIT with zero error code.
      Example: all statements of trans succeeded, connection lost and so implicit rollback:
      we don't want ER_NET* errors to be logged in the BEGIN/ROLLBACK events, while statement
      events have 0. If there was really a serious error code, it's already in the statement events.
      
      
      sql/log.cc:
        When we write the cached binlog segment to disk binlog at COMMIT/ROLLBACK time:
        imagine this is rollback due to net timeout, after all statements of
        the transaction succeeded. Then we want a zero-error code in BEGIN.
        In other words, if there was a really serious error code it's already
        in the transaction's statement events.
      sql/sql_table.cc:
        out of date comment
      38c6f97d
  13. 09 Nov, 2004 1 commit
  14. 08 Nov, 2004 1 commit
    • unknown's avatar
      mysql.h: · 689c8a9e
      unknown authored
        Adding a prototype for the new function.
      
      
      include/mysql.h:
        Adding a prototype for the new function.
      689c8a9e
  15. 05 Nov, 2004 9 commits
  16. 04 Nov, 2004 5 commits