An error occurred fetching the project authors.
  1. 09 Dec, 2004 1 commit
    • guilhem@mysql.com's avatar
      Changing the default of libmysqlclient : it's now NO reconnection. · 1cbc904c
      guilhem@mysql.com authored
      All our programs which use mysql_real_connect() and mysql_connect() are updated accordingly, though I have deliberately
      made mysqlimport not reconnect anymore (already true for mysqldump >= 4.1.8).
      All Connector devs have been warned about the change I'm doing here - which was agreed with Monty,
      and fixes BUG#2555.
      1cbc904c
  2. 19 Nov, 2004 1 commit
  3. 12 Nov, 2004 1 commit
  4. 04 Nov, 2004 1 commit
  5. 09 Sep, 2004 1 commit
    • monty@mysql.com's avatar
      After merge fixes of merge with 4.1 that included the new arena code. · f2829d03
      monty@mysql.com authored
      Fixed (together with Guilhem) bugs in mysqlbinlog regarding --offset
      Prefix addresses with 0x for easier comparisons of debug logs
      Fixed problem where MySQL choosed index-read even if there would be a much better range on the same index
      This fix changed some 'index' queries to 'range' queries in the test suite
      Don't create 'dummy' WHERE clause for trivial WHERE clauses where we can remove the WHERE clause.
      This fix removed of a lot of 'Using where' notes in the test suite.
      Give NOTE instead of WARNING if table/function doesn't exists when using DROP IF EXISTS
      Give NOTE instead of WARNING for safe field-type conversions
      f2829d03
  6. 31 Aug, 2004 1 commit
  7. 24 Aug, 2004 1 commit
  8. 23 Aug, 2004 1 commit
  9. 14 Aug, 2004 1 commit
    • rburnett@build.mysql.com's avatar
      mysql_priv.h: · 67003d1c
      rburnett@build.mysql.com authored
        Added declarations for print_msg_to_log and vprint_msg_to_log.  sql_print_error are simple functions that wrap calls to print_msg_to_log.  Define the different error types with MY_ERROR_TYPE, MY_WARNING_TYPE, and MY_INFORMATION_TYPE
      gen_lex_hash.cc:
        Added NULL error reporting parameter to handle_options
      log.cc:
        Add print_msg_to_log, print_buffer_to_log, and vprint_msg_to_log.  Print_msg_to_log will write the message to the windows event log if on NT.  We now have error, warning, and information versions of sql_print_xxxx.  T his is a variation of a similar changeset WAX did.
      mysqld.cc:
        Added option_error_reporter callback function and pass that into handle_options
      mysql.cc:
        Added NULL as error reporter arg to the end of handle_options
      Many files:
        Added NULL error reporter parameter as the last paramter to handle_options
      my_getopt.c:
        Added second function pointer to server as an error reporting callback.  Added local function report_option_error that will either write the error to stderr or to the error reporting callback.  changed all calls in handle_options from fprintf(stderr, ... ) to report_option_error
      my_getopt.h:
        Changed declaration of handle_options to use typedefs for the two function pointers.  added second function pointer to server as an error reporting callback
      mysqld.dsp:
        Added custom build step for compiling message file and added message resource file (output of mc)
      67003d1c
  10. 29 Jul, 2004 1 commit
    • guilhem@mysql.com's avatar
      WL#1580: --start-datetime, --stop-datetime, --start-position (alias for... · 0f3e279a
      guilhem@mysql.com authored
      WL#1580: --start-datetime, --stop-datetime, --start-position (alias for --position) and --stop-position
      options for mysqlbinlog, with a test file.
      This enables user to say "recover my database to how it was this morning at 10:30"
      (mysqlbinlog "--stop-datetime=2003-07-29 10:30:00").
      Using time functions into client/ made me move them out of sql/ into sql-common/.
      + (small) fix for BUG#4507 "mysqlbinlog --read-from-remote-server sometimes
      cannot accept 2 binlogs" (that is, on command line).
      0f3e279a
  11. 26 Jul, 2004 1 commit
  12. 17 Jul, 2004 1 commit
    • guilhem@mysql.com's avatar
      Fixes for · 88e00cd9
      guilhem@mysql.com authored
      BUG#4506 "mysqlbinlog --position --read-from-remote-server has wrong "# at" lines",
      BUG#4553 "Multi-table DROP TABLE replicates improperly for nonexistent table" with a test file.
      It was not possible to add a test for BUG#4506 as in the test suite we must use --short-form
      which does not display the "# at" lines.
      88e00cd9
  13. 10 Jun, 2004 1 commit
  14. 03 Jun, 2004 1 commit
  15. 25 May, 2004 1 commit
  16. 24 May, 2004 1 commit
  17. 23 May, 2004 1 commit
    • guilhem@mysql.com's avatar
      mysqlbinlog: new option --to-last-log. This option has effect only if --read-from-remote-server. · ce1e1f4c
      guilhem@mysql.com authored
      It causes mysqlbinlog to not stop after the end of the requested binlog, and instead read
      until the end of the last binlog of mysqld (beware of endless loops if you pipe this
      into the same mysqld).
      I.e. it enables back (at customer's request) what we considered (and I still do)
      as BUG#3204, but now with an option instead of being the default behaviour.
      The default behaviour is still to stop after the end of the requested binlog,
      whether --read-from-remote-server or not.
      ce1e1f4c
  18. 28 Apr, 2004 1 commit
  19. 18 Mar, 2004 2 commits
  20. 12 Mar, 2004 1 commit
  21. 11 Mar, 2004 2 commits
  22. 04 Mar, 2004 1 commit
  23. 23 Feb, 2004 1 commit
  24. 19 Feb, 2004 1 commit
  25. 16 Feb, 2004 1 commit
    • monty@mysql.com's avatar
      After merge fixes · f43093ec
      monty@mysql.com authored
      Added more DBUG statements
      Ensure that we are comparing end space with BINARY strings
      Use 'any_db' instead of '' to mean any database. (For HANDLER command)
      Only strip ' ' when comparing CHAR, not other space-like characters (like \t)
      f43093ec
  26. 13 Feb, 2004 1 commit
  27. 10 Feb, 2004 1 commit
  28. 06 Feb, 2004 1 commit
  29. 21 Dec, 2003 1 commit
  30. 19 Dec, 2003 1 commit
    • guilhem@gbichot2's avatar
      Now merge is done. · d67bbe72
      guilhem@gbichot2 authored
      For previous commit I had run only rpl* tests, here the other ones had a 
      few surprises. Latest status:
      - all tests pass
      - all replication tests pass with Valgrind
      This is the final-final commit & push.
      Doc remains.
      d67bbe72
  31. 18 Dec, 2003 1 commit
    • guilhem@gbichot2's avatar
      This will be pushed only after I fix the testsuite. · 66a32e89
      guilhem@gbichot2 authored
      This is the main commit for Worklog tasks:
       * A more dynamic binlog format which allows small changes (1064)
       * Log session variables in Query_log_event (1063)
      Below 5.0 means 5.0.0.
      MySQL 5.0 is able to replicate FOREIGN_KEY_CHECKS, UNIQUE_KEY_CHECKS (for speed),
      SQL_AUTO_IS_NULL, SQL_MODE. Not charsets (WL#1062), not some vars (I can only think
      of SQL_SELECT_LIMIT, which deserves a special treatment). Note that this
      works for queries, except LOAD DATA INFILE (for this it would have to wait
      for Dmitri's push of WL#874, which in turns waits for the present push, so...
      the deadlock must be broken!). Note that when Dmitri pushes WL#874 in 5.0.1,
      5.0.0 won't be able to replicate a LOAD DATA INFILE from 5.0.1.
      Apart from that, the new binlog format is designed so that it can tolerate
      a little variation in the events (so that a 5.0.0 slave could replicate a
      5.0.1 master, except for LOAD DATA INFILE unfortunately); that is, when I
      later add replication of charsets it should break nothing. And when I later
      add a UID to every event, it should break nothing.
      The main change brought by this patch is a new type of event, Format_description_log_event,
      which describes some lengthes in other event types. This event is needed for
      the master/slave/mysqlbinlog to understand a 5.0 log. Thanks to this event,
      we can later add more bytes to the header of every event without breaking compatibility.
      Inside Query_log_event, we have some additional dynamic format, as every Query_log_event
      can have a different number of status variables, stored as pairs (code, value); that's
      how SQL_MODE and session variables and catalog are stored. Like this, we can later
      add count of affected rows, charsets... and we can have options --don't-log-count-affected-rows
      if we want.
      MySQL 5.0 is able to run on 4.x relay logs, 4.x binlogs.
      Upgrading a 4.x master to 5.0 is ok (no need to delete binlogs),
      upgrading a 4.x slave to 5.0 is ok (no need to delete relay logs);
      so both can be "hot" upgrades.
      Upgrading a 3.23 master to 5.0 requires as much as upgrading it to 4.0.
      3.23 and 4.x can't be slaves of 5.0.
      So downgrading from 5.0 to 4.x may be complicated.
      Log_event::log_pos is now the position of the end of the event, which is
      more useful than the position of the beginning. We take care about compatibility
      with <5.0 (in which log_pos is the beginning).
      I added a short test for replication of SQL_MODE and some other variables.
      TODO:
      - after committing this, merge the latest 5.0 into it
      - fix all tests
      - update the manual with upgrade notes.
      66a32e89
  32. 01 Dec, 2003 1 commit
  33. 21 Oct, 2003 1 commit
    • guilhem@mysql.com's avatar
      Fix for Bug #1595 "mysqlbinlog can't read a password from the console". · c93f69e9
      guilhem@mysql.com authored
      ** I already fixed it in 3.23; I fix it in 4.0 separately because the
      code is a bit different (so the changeset 1.1422 of 3.23 should not be
      merged here) **
      Make mysqlbinlog prompt for the password if
      mysqlbinlog -p
      instead of printing the usage().
      This makes mysqlbinlog behave like other clients.
      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).
      c93f69e9
  34. 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
  35. 08 Oct, 2003 1 commit
  36. 07 Oct, 2003 2 commits
  37. 29 Sep, 2003 1 commit