1. 17 Sep, 2003 1 commit
  2. 15 Sep, 2003 1 commit
  3. 12 Sep, 2003 2 commits
    • greg@mysql.com's avatar
      cc6e3a2e
    • guilhem@mysql.com's avatar
      Quick backport of the following bugfix from MySQL 4.0.14. · 40a88045
      guilhem@mysql.com authored
      DO NOT COPY THIS CODE TO 4.0. The bugfix is better in 4.0,
      but here in 3.23 we don't want to add a new error code so
      we just use ER_EMPTY_QUERY. Bug was:
      "If a query was ignored on the slave (because of
      @code{replicate-ignore-table} and other similar rules), the slave
      still checked if the query got the same error code (0, no error) as on
      the master. So if the master had an error on the query (for example,
      ``Duplicate entry'' in a multiple-row insert), then the slave stopped
      and warned that the error codes didn't match. (Bug #797)"
      40a88045
  4. 11 Sep, 2003 1 commit
  5. 03 Sep, 2003 1 commit
  6. 02 Sep, 2003 2 commits
  7. 28 Aug, 2003 3 commits
  8. 21 Aug, 2003 3 commits
  9. 18 Aug, 2003 2 commits
  10. 12 Aug, 2003 1 commit
  11. 07 Aug, 2003 2 commits
  12. 06 Aug, 2003 1 commit
  13. 04 Aug, 2003 1 commit
  14. 03 Aug, 2003 1 commit
  15. 01 Aug, 2003 1 commit
  16. 28 Jul, 2003 1 commit
  17. 19 Jul, 2003 1 commit
  18. 01 Jul, 2003 2 commits
  19. 29 Jun, 2003 1 commit
  20. 26 Jun, 2003 2 commits
  21. 21 Jun, 2003 1 commit
    • guilhem@mysql.com's avatar
      Can't believe it: one more cset (04-27) which never found his way to the central · dcbcb785
      guilhem@mysql.com authored
      repository (incredible that I forgot to push, but why not).
      So unfortunately the bugfix missed 3.23.57 and will be in .58 :(
      Instead of looking like working (bug #198), replication between
      a 3.23 slave and 4.0 master should frankly stop. Here we detect
      4.0 masters in the 3.23 slave code when we see a strange Rotate
      event, and in that case we print an error and stop.
      4.0.13 and older masters will be "often" caught (see the patch); 4.0.14
      and newer masters will always be immediately caught.
      dcbcb785
  22. 19 Jun, 2003 2 commits
  23. 18 Jun, 2003 3 commits
  24. 16 Jun, 2003 2 commits
  25. 11 Jun, 2003 1 commit
    • heikki@hundin.mysql.fi's avatar
      os0file.c: · 2401227c
      heikki@hundin.mysql.fi authored
        Prevent on Windows starting of two mysqld instances on SAME InnoDB files: that could cause severe database corruption
      2401227c
  26. 08 Jun, 2003 1 commit