1. 19 Nov, 2004 1 commit
  2. 18 Nov, 2004 1 commit
  3. 17 Nov, 2004 1 commit
  4. 16 Nov, 2004 1 commit
    • unknown's avatar
      ha_innodb.cc: · 16d735ad
      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
      16d735ad
  5. 15 Nov, 2004 1 commit
    • unknown's avatar
      Proposed fix for bug #6439 "from_unixtime() function returns wrong datetime · e1509cf7
      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.
      e1509cf7
  6. 12 Nov, 2004 4 commits
  7. 11 Nov, 2004 4 commits
  8. 10 Nov, 2004 3 commits
    • unknown's avatar
      Merge paul@bk-internal.mysql.com:/home/bk/mysql-4.0 · 4bbec092
      unknown authored
      into kite-hub.kitebird.com:/src/extern/MySQL/bk/mysql-4.0
      
      
      4bbec092
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · 93cbaf03
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      
      93cbaf03
    • unknown's avatar
      Fix for BUG#6522 "Replication fails due to a rolled back transaction in the binlog" · 12fbc41f
      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
      12fbc41f
  9. 09 Nov, 2004 1 commit
  10. 08 Nov, 2004 1 commit
    • unknown's avatar
      mysql.h: · 01c80f55
      unknown authored
        Adding a prototype for the new function.
      
      
      include/mysql.h:
        Adding a prototype for the new function.
      01c80f55
  11. 05 Nov, 2004 9 commits
  12. 04 Nov, 2004 6 commits
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · 4a56b284
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      
      4a56b284
    • unknown's avatar
      Fix for BUG##5714 "Insert into MyISAM table and select ... for update]": · e30bd1e4
      unknown authored
      the fact that the transaction log is empty does not mean we're not in a transaction
      (it could be BEGIN; SELECT * FOR UPDATE FROM ibtable: then we don't want to commit now, even if
      the statement is a MyISAM update).
      With a testcase.
      
      
      mysql-test/r/mix_innodb_myisam_binlog.result:
        result update
      mysql-test/t/mix_innodb_myisam_binlog.test:
        test update for a new bug
      sql/log.cc:
        The fact that the transaction log is empty does not mean we're not in a transaction
        (it could be BEGIN; SELECT * FOR UPDATE: then we don't want to commit now).
      e30bd1e4
    • unknown's avatar
      Merge siva.hindu.god:/opt/home/tim/m/40/bk · 6ed9208e
      unknown authored
      into siva.hindu.god:/opt/home/tim/m/40/a
      
      
      configure.in:
        Auto merged
      6ed9208e
    • unknown's avatar
      b80ed3bb
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.0 · 1e87c820
      unknown authored
      into mysql.com:/home/dlenev/src/mysql-4.0-bg6387
      
      
      1e87c820
    • unknown's avatar
      The files stored in "Docs/Images" within the "mysqldocs" BK tree must be included · 0dd1ab1a
      unknown authored
      in the source tar-ball for distribution. This is done by using the "DISTFILES" macro
      in a new "Docs/Images/Makefile". As the source BK tree does not contain these files,
      they are copied from the "mysqldocs" tree at release build time.
      This changeset relies on "bk commit - mysqldoc tree (joerg:1.2276)" of today.
      
      
      Build-tools/Bootstrap:
        Copy the relevant files with "Docs/Images" from the "mysqldocs" BK tree into the
        build tree, ensuring that the "Makefile*" from the source BK tree are removed before.
      Docs/Images/Makefile.am:
        This dummy file is only needed to satisfy the Makefile hierarchy, 
        at release build time it will be replaced by its counterpart from the "mysqldocs" BK tree.
      Docs/Makefile.am:
        Include the new "Docs/Images/Makefile" in the Makefile hierarchy.
      configure.in:
        Ensure that the autotools will handle the new "Docs/Images/Makefile.am".
      0dd1ab1a
  13. 03 Nov, 2004 5 commits
    • unknown's avatar
      Merge jbruehe@bk-internal.mysql.com:/home/bk/mysql-4.0 · 7651674f
      unknown authored
      into mysql.com:/M40/mysql-4.0
      
      
      7651674f
    • unknown's avatar
      Fix for bug #6387 "Queried timestamp values do not match the inserted · d259ba40
      unknown authored
      value if server runs in time zone with leap seconds".
      
      Now in my_gmt_sec() function we take into account difference between
      our target and estimation in seconds part.
      
      
      mysql-test/Makefile.am:
        Added mysql-test/std_data/Moscow_leap reuired by new timezone3.test
        to source distribution.
      sql/time.cc:
        my_gmt_sec():
         When comparing our target broken-down datetime t value and proper 
         representation of our estimation *l_time we should take into account
         that they could differ in second part if we have time zone leap seconds.
         
         Also added comments about some assumptions used in this function.
      d259ba40
    • unknown's avatar
      InnoDB: fix bugs in the FOREIGN KEY parser (Bug #6340) · 0aa8d141
      unknown authored
      
      innobase/dict/dict0dict.c:
        dict_scan_to(): skip quoted strings while scanning for the keyword
        dict_create_foreign_constraints_low(): allow quote immediately after CONSTRAINT
      0aa8d141
    • unknown's avatar
      Merge marko@bk-internal.mysql.com:/home/bk/mysql-4.0 · 1d635090
      unknown authored
      into hundin.mysql.fi:/home/marko/k/mysql-4.0
      
      
      1d635090
    • unknown's avatar
      Portability fixes to mysqld_safe for non-Linux systems. Fix FIND_PROC · 1d3f4a1a
      unknown authored
      for Solaris test, and fix if @IS_LINUX@ test in mysqld_safe itself.
      
      
      configure.in:
        Portability fix for FIND_PROC setting; on Solaris (and
        probably others), 'ps -p $$' inside a shell script just
        returns 'sh' for command line, even though $0 contains
        the filename.  So, use 'ps -fp $$' in the test (it shows
        the full command line, e.g., 'sh configure').  Leave the
        actual FIND_PROC command as-is, since mysqld itself is
        not a shell script.
      scripts/mysqld_safe.sh:
        Portability fix for mysqld_safe on non-Linux systems.  A bogus use
        of 'if' and 'test' caused non-bash shells to enter a section meant
        to be run only on Linux systems.
      BitKeeper/etc/logging_ok:
        Logging to logging@openlogging.org accepted
      1d3f4a1a
  14. 02 Nov, 2004 1 commit
    • unknown's avatar
      ha_innodb.cc: · 9c06c80d
      unknown authored
        Backport Jan's fix of the LOAD DATA INFILE REPLACE duplicate key error bug (Bug #5835) to 4.0
      
      
      sql/ha_innodb.cc:
        Backport Jan's fix of the LOAD DATA INFILE REPLACE duplicate key error bug (Bug #5835) to 4.0
      9c06c80d
  15. 01 Nov, 2004 1 commit