1. 10 Nov, 2004 2 commits
    • 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
  2. 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
  3. 05 Nov, 2004 9 commits
  4. 04 Nov, 2004 6 commits
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · ef627770
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      ef627770
    • unknown's avatar
      Fix for BUG##5714 "Insert into MyISAM table and select ... for update]": · e2709f46
      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).
      e2709f46
    • unknown's avatar
      Merge siva.hindu.god:/opt/home/tim/m/40/bk · 18a7c952
      unknown authored
      into siva.hindu.god:/opt/home/tim/m/40/a
      
      
      configure.in:
        Auto merged
      18a7c952
    • unknown's avatar
      b3e00b67
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.0 · 8df8ffeb
      unknown authored
      into mysql.com:/home/dlenev/src/mysql-4.0-bg6387
      
      8df8ffeb
    • unknown's avatar
      The files stored in "Docs/Images" within the "mysqldocs" BK tree must be included · 3cbb64c3
      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".
      3cbb64c3
  5. 03 Nov, 2004 5 commits
    • unknown's avatar
      Merge jbruehe@bk-internal.mysql.com:/home/bk/mysql-4.0 · 18d12b5e
      unknown authored
      into mysql.com:/M40/mysql-4.0
      
      18d12b5e
    • unknown's avatar
      Fix for bug #6387 "Queried timestamp values do not match the inserted · f967003c
      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.
      f967003c
    • unknown's avatar
      InnoDB: fix bugs in the FOREIGN KEY parser (Bug #6340) · a19b8ec7
      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
      a19b8ec7
    • unknown's avatar
      Merge marko@bk-internal.mysql.com:/home/bk/mysql-4.0 · e5493270
      unknown authored
      into hundin.mysql.fi:/home/marko/k/mysql-4.0
      
      e5493270
    • unknown's avatar
      Portability fixes to mysqld_safe for non-Linux systems. Fix FIND_PROC · 18976d0d
      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
      18976d0d
  6. 02 Nov, 2004 1 commit
    • unknown's avatar
      ha_innodb.cc: · b7cd3f5e
      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
      b7cd3f5e
  7. 01 Nov, 2004 2 commits
  8. 31 Oct, 2004 1 commit
    • unknown's avatar
      row0mysql.c, pars0pars.c, eval0eval.c, dict0load.c, dict0dict.c, dict0crea.c: · 97ce1517
      unknown authored
        Fix bug #3478: InnoDB's FOREIGN KEY tables treated table and database names as case-insensitive; RENAME TABLE t to T would hang in an endless loop if t had a foreign key constraint defined on it
      dict0dict.c:
        Fix bug #3478: InnoDB's FOREIGN KEY tables treated table and database names as case-insensitive; RENAME TABLE t to T would hang in an endless loop if t had a foreign key constraint defined on it; fix also a hang that would occur if one tried in ALTER TABLE or RENAME TABLE to create a foreign key constraint name that collided with another existing name
      
      
      innobase/dict/dict0crea.c:
        Fix bug #3478: InnoDB's FOREIGN KEY tables treated table and database names as case-insensitive; RENAME TABLE t to T would hang in an endless loop if t had a foreign key constraint defined on it
      innobase/dict/dict0load.c:
        Fix bug #3478: InnoDB's FOREIGN KEY tables treated table and database names as case-insensitive; RENAME TABLE t to T would hang in an endless loop if t had a foreign key constraint defined on it
      innobase/dict/dict0dict.c:
        Fix bug #3478: InnoDB's FOREIGN KEY tables treated table and database names as case-insensitive; RENAME TABLE t to T would hang in an endless loop if t had a foreign key constraint defined on it; fix also a hang that would occur if one tried in ALTER TABLE or RENAME TABLE to create a foreign key constraint name that collided with another existing name
      innobase/eval/eval0eval.c:
        Fix bug #3478: InnoDB's FOREIGN KEY tables treated table and database names as case-insensitive; RENAME TABLE t to T would hang in an endless loop if t had a foreign key constraint defined on it
      innobase/pars/pars0pars.c:
        Fix bug #3478: InnoDB's FOREIGN KEY tables treated table and database names as case-insensitive; RENAME TABLE t to T would hang in an endless loop if t had a foreign key constraint defined on it
      innobase/row/row0mysql.c:
        Fix bug #3478: InnoDB's FOREIGN KEY tables treated table and database names as case-insensitive; RENAME TABLE t to T would hang in an endless loop if t had a foreign key constraint defined on it
      97ce1517
  9. 29 Oct, 2004 1 commit
  10. 28 Oct, 2004 1 commit
  11. 27 Oct, 2004 7 commits
    • unknown's avatar
      Merge lgrimmer@bk-internal.mysql.com:/home/bk/mysql-4.0 · bb1cb112
      unknown authored
      into mysql.com:/space/my/mysql-4.0
      
      bb1cb112
    • unknown's avatar
      - Applied some Windows portability fixes for myisampack.c and sql_handler.cc · f4b0f729
      unknown authored
        (backports from fixes made in 4.1)
      
      
      myisam/myisampack.c:
         - replaced "1ULL" with "((ulonglong)1)" to resolve a compile error on
           Windows
      sql/sql_handler.cc:
         - removed some unused variables
         - added a (byte*) cast to fix a compile error on Windows (backport of a
           fix made in 4.1)
      f4b0f729
    • unknown's avatar
      texi2html: · 31c366cb
      unknown authored
        Updated version of texi2html so that 4.0.22 HTML manual doesn't turn out all goofy.
      
      
      Docs/Support/texi2html:
        Updated version of texi2html so that 4.0.22 HTML manual doesn't turn out all goofy.
      31c366cb
    • unknown's avatar
      Merge jbruehe@bk-internal.mysql.com:/home/bk/mysql-4.0 · c92c6789
      unknown authored
      into mysql.com:/M40/mysql-4.0
      
      c92c6789
    • unknown's avatar
      Fix when compiling without InnoDB · 89dce2fb
      unknown authored
      
      BitKeeper/deleted/.del-innodb-lock-master.opt~f76a4a1999728f87:
        Delete: mysql-test/t/innodb-lock-master.opt
      89dce2fb
    • unknown's avatar
      Change 'Build-tools/mysql-copyright' to ensure the receiving machines will build · 0b1b06e3
      unknown authored
      without trying to re-run autotools.
      (Backport from 4.1.7 for 4.0.22)
      
      
      Build-tools/mysql-copyright:
        The top level Makefile will try to re-run the autotools unless the timestamps of the
        relevant files are in truly ascending order. Ensure this order!
        (Backport from 4.1.7 for 4.0.22)
      0b1b06e3
    • unknown's avatar
      Backport innodb_max_purge_lag from 4.1 · 2d4bea72
      unknown authored
      
      innobase/include/srv0srv.h:
        Add configuration parameter srv_max_purge_lag.
        Add global variable srv_dml_needed_delay.
      innobase/include/trx0sys.h:
        Add trx_sys->rseg_history_len
      innobase/row/row0mysql.c:
        Add row_mysql_delay_if_needed() for delaying INSERTs, UPDATEs and
        DELETEs for srv_dml_needed_delay microseconds.
      innobase/srv/srv0srv.c:
        Define global variable srv_dml_needed_delay.
        Define configuration parameter srv_max_purge_lag.
      innobase/trx/trx0purge.c:
        Update trx_sys->rseg_history_len.
        trx_purge(): Compute srv_dml_needed_delay from srv_max_purge_lag
        and trx_sys->rseg_history_len.
      innobase/trx/trx0rseg.c:
        Initialize trx_sys->rseg_history_len at InnoDB start-up.
      sql/ha_innodb.h:
        Add configuration parameter srv_max_purge_lag.
      sql/mysqld.cc:
        Add startup option innodb_max_purge_lag,
        with default value 0 (meaning infinite, disabling the feature).
      sql/set_var.cc:
        Add global variable innodb_max_purge_lag.
      2d4bea72
  12. 24 Oct, 2004 1 commit
  13. 22 Oct, 2004 3 commits