1. 24 Nov, 2003 1 commit
  2. 19 Nov, 2003 1 commit
    • serg@serg.mylan's avatar
      ignore: · 201f2770
      serg@serg.mylan authored
        added sql/udf_example.so scripts/make_win_src_distribution
      201f2770
  3. 17 Nov, 2003 2 commits
  4. 04 Nov, 2003 1 commit
  5. 20 Oct, 2003 1 commit
    • guilhem@mysql.com's avatar
      Fix for Bug #1595 "mysqlbinlog can't read a password from the console". · d0a21a0a
      guilhem@mysql.com 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).
      d0a21a0a
  6. 18 Oct, 2003 1 commit
  7. 08 Oct, 2003 2 commits
  8. 07 Oct, 2003 1 commit
  9. 06 Oct, 2003 1 commit
  10. 29 Sep, 2003 1 commit
  11. 27 Sep, 2003 1 commit
    • guilhem@mysql.com's avatar
      backport of a fix made in 4.0 to make replication work in 64-bit binaries. · bf5be93a
      guilhem@mysql.com 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).
      bf5be93a
  12. 17 Sep, 2003 1 commit
  13. 15 Sep, 2003 1 commit
  14. 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
  15. 11 Sep, 2003 1 commit
  16. 03 Sep, 2003 1 commit
  17. 02 Sep, 2003 2 commits
  18. 28 Aug, 2003 3 commits
  19. 21 Aug, 2003 3 commits
  20. 18 Aug, 2003 2 commits
  21. 12 Aug, 2003 1 commit
  22. 07 Aug, 2003 2 commits
  23. 06 Aug, 2003 1 commit
  24. 04 Aug, 2003 1 commit
  25. 03 Aug, 2003 1 commit
  26. 01 Aug, 2003 1 commit
  27. 28 Jul, 2003 1 commit
  28. 19 Jul, 2003 1 commit
  29. 01 Jul, 2003 2 commits