1. 04 Nov, 2003 1 commit
    • unknown's avatar
      compile-pentium-gcov: · e6298f37
      unknown authored
        Stop the line wrapping for warnings.
        it needs for warnings statistic in code coverage
      
      
      BUILD/compile-pentium-gcov:
        Stop the line wrapping for warnings.
        it needs for warnings statistic in code coverage
      e6298f37
  2. 20 Oct, 2003 1 commit
    • unknown's avatar
      Fix for Bug #1595 "mysqlbinlog can't read a password from the console". · 409b8f35
      unknown authored
      Make mysqlbinlog prompt for the password if
      mysqlbinlog -p
      instead of printing the usage().
      This makes mysqlbinlog behave like other clients, which is the reason
      why we fix this in 3.23.
      This new code was almost copied from mysqldump.
      Note that before, one could use
      mysqlbinlog -p pass
      and now one must use
      mysqlbinlog -ppass
      (putting a space will ask for the password).
      
      
      client/mysqlbinlog.cc:
        Make mysqlbinlog prompt for the password if
        mysqlbinlog -p
        instead of printing the usage().
        This makes mysqlbinlog behave like other clients, which is the reason
        why we fix this in 3.23.
        This new code was almost copied from mysqldump.
        Note that before, one could use
        mysqlbinlog -p pass
        and now one must use
        mysqlbinlog -ppass
        (putting a space will ask for the password).
      409b8f35
  3. 18 Oct, 2003 1 commit
  4. 08 Oct, 2003 2 commits
  5. 07 Oct, 2003 1 commit
  6. 06 Oct, 2003 1 commit
  7. 29 Sep, 2003 1 commit
  8. 27 Sep, 2003 1 commit
    • unknown's avatar
      backport of a fix made in 4.0 to make replication work in 64-bit binaries. · 52d80b76
      unknown authored
      The 4.0 changeset was:
      ChangeSet@1.1579.3.1, 2003-09-26 23:43:22+02:00, guilhem@mysql.com
        Fix for 64-bit machines.
        I am almost sure this is the cause for
        BUG#1381 [Opn]: Bug in replication on HP-UX 64 bit binaries?
        BUG#1256 [CRp]: Replication slave fails to connect to master in 64-bit version
       (Solaris)
        The reason why I think it's wrong is that the normal client code has
        uint32 ip_addr.
        (of course on 32-bit machines it does not matter, but on 64-bit it does).
      
      
      
      sql/mini_client.cc:
        backport of a fix made in 4.0 to make replication work in 64-bit binaries.
      52d80b76
  9. 17 Sep, 2003 1 commit
  10. 15 Sep, 2003 1 commit
  11. 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
  12. 11 Sep, 2003 1 commit
  13. 03 Sep, 2003 1 commit
  14. 02 Sep, 2003 2 commits
  15. 28 Aug, 2003 3 commits
  16. 21 Aug, 2003 3 commits
  17. 18 Aug, 2003 2 commits
  18. 12 Aug, 2003 1 commit
  19. 07 Aug, 2003 2 commits
  20. 06 Aug, 2003 1 commit
  21. 04 Aug, 2003 1 commit
  22. 03 Aug, 2003 1 commit
  23. 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
  24. 28 Jul, 2003 1 commit
  25. 19 Jul, 2003 1 commit
  26. 01 Jul, 2003 2 commits
  27. 29 Jun, 2003 1 commit
  28. 26 Jun, 2003 2 commits
  29. 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