An error occurred fetching the project authors.
  1. 20 Feb, 2007 1 commit
  2. 19 Feb, 2007 2 commits
  3. 22 Jan, 2007 1 commit
  4. 22 Dec, 2006 1 commit
  5. 14 Dec, 2006 3 commits
  6. 07 Dec, 2006 1 commit
  7. 28 Nov, 2006 1 commit
  8. 30 Aug, 2006 1 commit
    • aelkin/elkin@andrepl.dsl.inet.fi's avatar
      Changes made according to HLD/LLD. · 7be4bc4e
      aelkin/elkin@andrepl.dsl.inet.fi authored
         The following is an excerption from the WL.
            
         1. Change so that MIXED is default format
            1.1 to change the default for command line --binlog-format
            1.2 to alter global_system_variables.binlog_format calculation
                basing on command line --binlog-format parameter and 
                its default.
         2. Change test suite so that more testing is done by MIXED format.
            2.1 to check if there are test cases requiring --binlog-foramt=statement via
                `source include/have_binlog_format_statement.inc' and affected by 
                altering the latter to be "mixed".
            2.2 to check the content of such vulnerable cases to find if
                extending to the mixed does not modify results. In that case simply
                substitute source arguments as explained.
            2.3 if a test in mixed mode deals with features triggering
                row-binlogging then if necessary we can switch explicitly
                to statement mode or create another test to run with 
                non-recommended STATEMENT mode
         
                Particullarily, extracting INSERT DELAYED 
                binlogging subtest for statement mode is performed, and 
                the snippet is moved into a separate test file.
                Note that since now all three modes verify this use case
                through 3 different tests.
         
         No changes in item 3 of HLD appeared to be needed.
      7be4bc4e
  9. 26 Jul, 2006 1 commit
  10. 24 Jul, 2006 1 commit
  11. 31 May, 2006 2 commits
  12. 28 May, 2006 1 commit
  13. 20 May, 2006 1 commit
  14. 16 May, 2006 1 commit
  15. 14 May, 2006 1 commit
  16. 13 May, 2006 1 commit
  17. 09 May, 2006 1 commit
    • aelkin@mysql.com's avatar
      BUG#14157: utf8 encoding in binlog without set character_set_client e.g DROP temporary · 226d978a
      aelkin@mysql.com authored
      Binlog lacks encoding info about DROPped temporary table.
      
      Idea of the fix is to switch temporary to system_charset_info when a temporary table
      is DROPped for binlog. Since that is the server, that automatically, but not the client, who generates the query
      the binlog should be updated on the server's encoding for the coming DROP.
      The `write_binlog_with_system_charset()' is introduced to replace similar problematic places in the code.
      226d978a
  18. 10 Feb, 2006 1 commit
  19. 09 Feb, 2006 1 commit
    • aelkin@mysql.com's avatar
      BUG#16217 forced to introduce a separate mysql client command to adopt its · dd2a44c4
      aelkin@mysql.com authored
      internal charset to one associated with currently being handled query. 
      To note such a query can come from interactive client either.
      
      There was a discussion within replication team and Monty who's suggestion won.
      It avoids straightforward parsing of all `set' queries that could affect client side 
      character set. 
      According to the idea, mysql client does not parse `set' queries but rather cares of
      `charset new_cs_name' command.
      This command is generated by mysqlbinlog in form of exclaiming comment (Lars' suggestion)
      so that enlightened clients like `mysql' knows what to do with it.
      
      Interactive human can switch between many multi-byte charsets during the session 
      providing the command explicitly. 
      To note that setting new internal mysql's charset does not
      trigger sending any `SET' sql statement to the server. 
      dd2a44c4
  20. 24 Jan, 2006 1 commit
  21. 22 Dec, 2005 1 commit
  22. 24 Sep, 2005 1 commit
    • kent@mysql.com's avatar
      mysqlbinlog.test: · 4e289272
      kent@mysql.com authored
        Windows have no 'cat' command, use <
      mysql.test:
        Windows can't handle single quotes in --exec line
      4e289272
  23. 28 Jul, 2005 1 commit
  24. 30 Mar, 2005 1 commit
  25. 25 Mar, 2005 1 commit
    • gbichot@quadita2.mysql.com's avatar
      WWe now store the catalog in Query_log_event in binlog WITHOUT its end zero. · ead47f47
      gbichot@quadita2.mysql.com authored
      This saves one byte per Query_log_event on disk compared to 5.0.[0..3]. Compatibility problems with 5.0.x where x<4
      are explained in the comments in log_event.cc. Putting back s/my_open(O_TRUNC)/(my_delete+my_create) change which had
      been wiped away by somebody doing a wrong 4.1->5.0 merge (which happened just
      before 5.0.3 :( ). Applying it to new events for LOAD DATA INFILE.
      If slave fails in Execute_load_query_log_event::exec_event(),
      don't delete the file (so that it's re-usable at next START SLAVE).
      And (youpi!) fix for BUG#3247 "a partially completed LOAD DATA INFILE is not
      executed at all on the slave" (storing an Execute_load_query_log_event
      to binlog, with its error code, instead of Delete_file_log_event).
      ead47f47
  26. 16 Mar, 2005 1 commit
    • dlenev@brandersnatch.localdomain's avatar
      WL#874 "Extended LOAD DATA". · f1691140
      dlenev@brandersnatch.localdomain authored
      Now one can use user variables as target for data loaded from file
      (besides table's columns). Also LOAD DATA got new SET-clause in which
      one can specify values for table columns as expressions.
      
      For example the following is possible:
      LOAD DATA INFILE 'words.dat' INTO TABLE t1 (a, @b) SET c = @b + 1;
      
      This patch also implements new way of replicating LOAD DATA.
      Now we do it similarly to other queries.
      We store LOAD DATA query in new Execute_load_query event
      (which is last in the sequence of events representing LOAD DATA).
      When we are executing this event we simply rewrite part of query which
      holds name of file (we use name of temporary file) and then execute it
      as usual query. In the beggining of this sequence we use Begin_load_query
      event which is almost identical to Append_file event
      f1691140
  27. 04 Feb, 2005 1 commit
  28. 16 Jan, 2005 1 commit
  29. 09 Jun, 2004 1 commit
    • guilhem@mysql.com's avatar
      Making DROP TABLE IF EXISTS, DROP DATABASE IF EXISTS, DELETE FROM, UPDATE be logged to · 2b20e84f
      guilhem@mysql.com authored
      binlog even if they changed nothing, and a test for this.
      This is useful when users use these commands to clean up their master and slave by issuing
      one command on master (assume master and slave have slightly different data for some
      reason and you want to clean up both).
      Note that I have not changed multi-table DELETE and multi-table UPDATE because their
      error-reporting mechanism is more complicated.
      2b20e84f
  30. 18 Mar, 2004 1 commit
  31. 06 Feb, 2004 1 commit
  32. 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
  33. 31 Oct, 2003 1 commit
  34. 08 Oct, 2003 3 commits