An error occurred fetching the project authors.
  1. 26 Jul, 2006 1 commit
  2. 24 Jul, 2006 1 commit
  3. 28 May, 2006 1 commit
  4. 20 May, 2006 1 commit
  5. 14 May, 2006 1 commit
  6. 13 May, 2006 1 commit
  7. 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
  8. 10 Feb, 2006 1 commit
  9. 28 Jul, 2005 1 commit
  10. 30 Mar, 2005 1 commit
  11. 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
  12. 18 Mar, 2004 1 commit
  13. 06 Feb, 2004 1 commit
  14. 31 Oct, 2003 1 commit
  15. 08 Oct, 2003 4 commits
  16. 29 Sep, 2003 2 commits
  17. 24 Sep, 2003 1 commit
    • dlenev@mysql.com's avatar
      Test for mysqlbinlog · 977c7b2d
      dlenev@mysql.com authored
      Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec
      event without seeing Create_file event before
      977c7b2d