1. 17 Sep, 2003 1 commit
  2. 15 Sep, 2003 1 commit
  3. 12 Sep, 2003 2 commits
    • unknown's avatar
      New Windows source package automation for 3.23 · dcf6e50d
      unknown authored
      
      VC++Files/InstallShield/3.23.XX-com/Component Definitions/.fgl:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/Component Definitions/Default.cdf:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/Component Definitions/Default.fgl:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/File Groups/Clients and Tools.fgl:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/File Groups/Default.fdf:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/File Groups/Default.fgl:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/File Groups/Development.fgl:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/File Groups/Documentation.fgl:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/File Groups/Grant Tables.fgl:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/File Groups/Servers.fgl:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/MySQL 3.23.com.ipr:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/Registry Entries/Default.rge:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/Script Files/Setup.dbg:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/Script Files/Setup.ino:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/Script Files/Setup.ins:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/Script Files/Setup.obs:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/Script Files/Setup.rul:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/Setup Files/Uncompressed Files/Language Independent/OS Independent/SETUP.BMP:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/Shell Objects/Default.shl:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/String Tables/Default.shl:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/Text Substitutions/Build.tsb:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/Text Substitutions/Setup.tsb:
        mvdir
      VC++Files/InstallShield/3.23.XX-com/Setup Files/Compressed Files/Language Independent/OS Independent/infolist.txt:
        Add version placeholders for automation
      VC++Files/InstallShield/3.23.XX-com/String Tables/0009-English/value.shl:
        Add version placeholders for automation
      VC++Files/InstallShield/3.23.XX-gpl/Setup Files/Compressed Files/Language Independent/OS Independent/infolist.txt:
        Add version placeholders for automation
      VC++Files/InstallShield/3.23.XX-gpl/String Tables/0009-English/value.shl:
        Add version placeholders for automation
      scripts/Makefile.am:
        Build make_win_src_distribution script by default
      BitKeeper/etc/logging_ok:
        Logging to logging@openlogging.org accepted
      dcf6e50d
    • unknown's avatar
      Quick backport of the following bugfix from MySQL 4.0.14. · 8cc642d7
      unknown 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)"
      
      
      sql/slave.cc:
        Ignore ER_EMPTY_QUERY as it is also a marker for "query was ignored because 
        of replicate-*-table rules".
      sql/sql_parse.cc:
        In a slave thread, mark an ignored query (because of replicate-*-table rules)
        as empty. The caller, exec_event(), will understand this error code as "ignorable
        query, don't compare the error codes on master and slave".
      8cc642d7
  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
    • unknown's avatar
      Backporting the changeset below from 4.0, because a customer hits · 2c3f6568
      unknown authored
      the bug with 3.23.
      ChangeSet@1.1416.113.1, 2003-03-22 15:22:59+01:00, guilhem@mysql.com
        Fix for #178  Replicating INSERT VALUES(USER()) crashes (SEGV) the slave
            Now it does not SEGV, but USER() is still badly replicated
            (it is replicated to ""), which is a lower priority bug.
      
      
      sql/item_strfunc.cc:
        Don't segfault in USER() if thd->user == 0 (system thread).
      2c3f6568
  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
    • unknown's avatar
      Can't believe it: one more cset (04-27) which never found his way to the central · 71438155
      unknown 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.
      
      
      sql/slave.cc:
        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.
      71438155
  22. 19 Jun, 2003 2 commits
  23. 18 Jun, 2003 3 commits
  24. 16 Jun, 2003 2 commits
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-3.23 · 714bf070
      unknown authored
      into mysql.com:/home/mysql_src/mysql-3.23
      
      
      714bf070
    • unknown's avatar
      Do not use 'created' for time anymore in Start_log_event, it's the same · 418fcdf1
      unknown authored
      as the already-stored timestamp. Now 'created' is used only to know if
      this is a first binlog or not. And we may re-use the superfluous bytes
      in 5.0 when we need room.
      
      
      sql/log_event.cc:
        This sort of reverts a change I made in 3.23.57. In 3.23.57 I set 'created' to 0
        if this was a non-first binlog, so I made mysqlbinlog not print the "created xx"
        part if created == 0. While this was sensible, as 'created' is 0 or equal to
        the timestamp which is already stored in the event, we can always print
        "created xx" by using the timestamp, and leaving the use of 'created' only to
        know if this is a first binlog or not (which we print as "created at startup").
      sql/log_event.h:
        In Start_log_event, 'created' is always the same as 'when', or O.
        We didn't need 4 bytes for this, a bit would have been enough (O or
        "same as 'when'"). Possibly in 5.0 we will re-use the useless bytes.
      418fcdf1
  25. 11 Jun, 2003 1 commit
    • unknown's avatar
      os0file.c: · a18c4883
      unknown authored
        Prevent on Windows starting of two mysqld instances on SAME InnoDB files: that could cause severe database corruption
      
      
      innobase/os/os0file.c:
        Prevent on Windows starting of two mysqld instances on SAME InnoDB files: that could cause severe database corruption
      a18c4883
  26. 08 Jun, 2003 1 commit
    • unknown's avatar
      Translation updated · 87473e96
      unknown authored
      
      BitKeeper/etc/logging_ok:
        Logging to logging@openlogging.org accepted
      87473e96