1. 20 Jun, 2003 1 commit
  2. 18 Jun, 2003 5 commits
  3. 17 Jun, 2003 4 commits
  4. 16 Jun, 2003 4 commits
  5. 15 Jun, 2003 4 commits
  6. 14 Jun, 2003 4 commits
  7. 13 Jun, 2003 1 commit
  8. 12 Jun, 2003 8 commits
  9. 11 Jun, 2003 4 commits
  10. 10 Jun, 2003 3 commits
    • guilhem@mysql.com's avatar
      Merge gbichot@213.136.52.20:/home/bk/mysql-4.0 · 27c70dc8
      guilhem@mysql.com authored
      into mysql.com:/home/mysql_src/mysql-4.0
      27c70dc8
    • guilhem@mysql.com's avatar
      More error messages. This is intended to help debugging; presently I have a · 96c8d91a
      guilhem@mysql.com authored
      support issue with an unclear message which can have N reasons for appearing.
      This should help us know at which point it failed, and get the errno when
      my_open was involved (as the reason for the unclear message is often a
      permission problem).
      RESET SLAVE resets last_error and last_errno in SHOW SLAVE STATUS (without this,
      rpl_loaddata.test, which is expected to generate an error in last_error, influenced
      rpl_log_pos.test).
      A small test update.
      Added STOP SLAVE to mysql-test-run to get rid of several stupid error messages
      which are printed while the master restarts and the slave attempts/manages to
      connect to it and sends it nonsense binlog requests.
      96c8d91a
    • monty@narttu.mysql.fi's avatar
      Don't install signal handler for SIGINT by default · d640ff4a
      monty@narttu.mysql.fi authored
      Added option --gdb
      Free memory used by replicate_xxx and binglog_xxx options
      d640ff4a
  11. 06 Jun, 2003 2 commits
    • guilhem@mysql.com's avatar
      Merge gbichot@213.136.52.20:/home/bk/mysql-4.0 · f4c70678
      guilhem@mysql.com authored
      into mysql.com:/home/mysql_src/mysql-4.0
      f4c70678
    • guilhem@mysql.com's avatar
      Fix for bug 254 : · 60fb005e
      guilhem@mysql.com authored
      we now make a distinction between if the master is < 3.23.57, 3.23 && >=57, and 4.x
      (before the 2 3.23 were one). This is because in 3.23.57 we have a way to distinguish between
      a Start_log_event written at server startup and one written at FLUSH LOGS, so we
      have a way to know if the slave must drop old temp tables or not.
      Change: mi->old_format was bool, now it's enum (to handle 3 cases). However, functions
      which had 'bool old_format' as an argument have their prototypes unchanged, because
      the old old_format == 0 now corresponds to the enum value BINLOG_FORMAT_CURRENT which
      is equal to 0, so boolean tests are left untouched. The only case were we use mi->old_format
      as an enum instead of casting it implicitly to a bool, is in Start_log_event::exec_event,
      where we want to distinguish between the 3 possible enum values.
      60fb005e