1. 07 Aug, 2003 6 commits
  2. 06 Aug, 2003 6 commits
  3. 05 Aug, 2003 2 commits
  4. 04 Aug, 2003 2 commits
    • unknown's avatar
      Fix VC++ compiler error · 89dad4c9
      unknown authored
      89dad4c9
    • unknown's avatar
      2 bugfixes: · d8df84aa
      unknown authored
      - Bug #985: "Between RESET SLAVE and START SLAVE, SHOW SLAVE STATUS is wrong."
      Now RESET SLAVE puts correct info in mi->host etc. A new test rpl_reset_slave
      for that.
      - Bug #986: "CHANGE MASTER & START SLAVE do not reset error columns in SHOW
      SLAVE STATUS". Now these reset the errors.
      
      
      mysql-test/r/rpl_loaddata.result:
        result update.
      mysql-test/t/rpl_loaddata.test:
        Test that RESET SLAVE, START SLAVE and CHANGE MASTER all reset 
        Last_slave_error and Last_slave_errno (columns of SHOW SLAVE STATUS).
        We do it in this test because that's one of tests which have 
        an intentional query error on the slave.
      sql/slave.cc:
        As we need TWICE the code to copy command-line options (--master-host etc)
        to mi (we already had it in init_master_info, but we also need it in RESET
        SLAVE to fix bug#985), I make a function of this code.
        And a function to reset Last_slave_error and Last_slave_errno (we need
        it in CHANGE MASTER, RESET SLAVE, and at the start of the SQL thread).
      sql/slave.h:
        declarations for new functions.
      sql/sql_repl.cc:
        copy --master-host etc to mi in RESET SLAVE, so that SHOW SLAVE STATUS
        shows correct information.
      d8df84aa
  5. 03 Aug, 2003 1 commit
  6. 02 Aug, 2003 3 commits
    • unknown's avatar
      Fix so that SET PASSWORD is not replicated by the slave if running with · 3b013646
      unknown authored
      replicate-*-table rules which exclude 'mysql' tables
      (e.g. replicate-wild-ignore-table=mysql.%).
      This was already the behaviour for GRANT/REVOKE, I'm extending it to
      SET PASSWORD because it seems very logical (the contrary seems illogical).
      2 new tests:
      - one to test if GRANT and SET PASSWORD are replicated
      - one to test if they are not replicated if replicate-wild-ignore-table=mysql.%
      The 2nd is also a testcase for BUG#980.
      
      
      sql/sql_acl.cc:
        Fix so that SET PASSWORD is not replicated by the slave if running with
        replicate-*-table rules which exclude 'mysql' tables
        (e.g. replicate-wild-ignore-table=mysql.%).
        This was already the behaviour for GRANT/REVOKE, I'm extending it to
        SET PASSWORD because it seems very logical (the contrary seems illogical).
      3b013646
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · b1c56d68
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      
      sql/sql_acl.cc:
        Auto merged
      b1c56d68
    • unknown's avatar
      Mark tables 'updating' in sql_acl.cc (mysql_grant(), mysql_table_grant()) so that · 5a696ebd
      unknown authored
      tables_ok() does not ignore them. This fixes random bug #980.
      
      
      sql/sql_acl.cc:
        Mark tables 'updating' so that tables_ok() does not ignore them;
        this fixes random bug #980.
      5a696ebd
  7. 01 Aug, 2003 6 commits
  8. 31 Jul, 2003 1 commit
  9. 30 Jul, 2003 4 commits
  10. 29 Jul, 2003 2 commits
    • unknown's avatar
      Fix security bug. mysqld server without ssl support was completly · 880088ba
      unknown authored
      ignorant about ssl_type attribute
      
      
      sql/sql_acl.cc:
        Now acl_getroot() honors ssl_type attribute even if we compile without openssl
      BitKeeper/etc/logging_ok:
        Logging to logging@openlogging.org accepted
      880088ba
    • unknown's avatar
      dict0dict.c: · 30b751f8
      unknown authored
        Fix bug introduced in 4.0.13 and reported by Emic: if a CREATE TABLE ended in a comment, a memory overrun could happen
      
      
      innobase/dict/dict0dict.c:
        Fix bug introduced in 4.0.13 and reported by Emic: if a CREATE TABLE ended in a comment, a memory overrun could happen
      30b751f8
  11. 28 Jul, 2003 3 commits
  12. 26 Jul, 2003 2 commits
  13. 25 Jul, 2003 2 commits
    • unknown's avatar
      srv0srv.c, os0file.c, log0recv.h, log0log.h, fil0fil.h, fsp0fsp.c, fil0fil.c: · df5b0889
      unknown authored
        Merge
      trx0trx.c:
        Print more info about a trx in SHOW INNODB status; try to find the bug reported by Plaxo
      buf0buf.c:
        Check that page log sequence numbers are not in the future
      log0recv.c, log0log.c:
        Fixed a bug: if you used big BLOBs, and your log files were relatively small, InnoDB could in a big BLOB operation temporarily write over the log produced AFTER the latest checkpoint. If InnoDB would crash at that moment, then the crash recovery would fail, because InnoDB would not be able to scan the log even up to the latest checkpoint. Starting from this version, InnoDB tries to ensure the latest checkpoint is young enough. If that is not possible, InnoDB prints a warning to the .err log
      
      
      innobase/log/log0log.c:
        Fixed a bug: if you used big BLOBs, and your log files were relatively small, InnoDB could in a big BLOB operation temporarily write over the log produced AFTER the latest checkpoint. If InnoDB would crash at that moment, then the crash recovery would fail, because InnoDB would not be able to scan the log even up to the latest checkpoint. Starting from this version, InnoDB tries to ensure the latest checkpoint is young enough. If that is not possible, InnoDB prints a warning to the .err log
      innobase/log/log0recv.c:
        Fixed a bug: if you used big BLOBs, and your log files were relatively small, InnoDB could in a big BLOB operation temporarily write over the log produced AFTER the latest checkpoint. If InnoDB would crash at that moment, then the crash recovery would fail, because InnoDB would not be able to scan the log even up to the latest checkpoint. Starting from this version, InnoDB tries to ensure the latest checkpoint is young enough. If that is not possible, InnoDB prints a warning to the .err log
      innobase/buf/buf0buf.c:
        Check that page log sequence numbers are not in the future
      innobase/trx/trx0trx.c:
        Print more info about a trx in SHOW INNODB status; try to find the bug reported by Plaxo
      innobase/fil/fil0fil.c:
        Merge
      innobase/fsp/fsp0fsp.c:
        Merge
      innobase/include/fil0fil.h:
        Merge
      innobase/include/log0log.h:
        Merge
      innobase/include/log0recv.h:
        Merge
      innobase/os/os0file.c:
        Merge
      innobase/srv/srv0srv.c:
        Merge
      df5b0889
    • unknown's avatar
      2763b52d