1. 03 Feb, 2005 4 commits
    • guilhem@mysql.com's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-5.0 · ac053d80
      guilhem@mysql.com authored
      into mysql.com:/home/mysql_src/mysql-5.0-clean
      ac053d80
    • guilhem@mysql.com's avatar
      WL#1062 "log charset info into all Query_log_event": · ed1696f6
      guilhem@mysql.com authored
      we store 7 bytes (1 + 2*3) in every Query_log_event.
      In the future if users want binlog optimized for small size and less safe,
      we could add --binlog-no-charset (and binlog-no-sql-mode etc): charset info
      is something by design optional (even if for now we don't offer possibility to disable it):
      it's not a binlog format change.
      We try to reduce the number of get_charset() calls in the slave SQL thread to a minimum
      by caching the charset read from the previous event (which will often be equal to the one of the current event).
      We don't use SET ONE_SHOT for charset-aware repl (we still do for timezones, will be fixed later).
      No more errors if one changes the global value of charset vars on master or slave
      (as we log charset info in all Query_log_event).
      Not fixing Load_log_event as it will be rewritten soon by Dmitri.
      Testing how mysqlbinlog behaves in rpl_charset.test.
      mysqlbinlog needs to know where charset file is (to be able to convert a charset number found
      in binlog (e.g. in User_var_log_event) to a charset name); mysql-test-run needs to pass
      the correct value for this option to mysqlbinlog.
      Many result udpates (adding charset info into every event shifts log_pos in SHOW BINLOG EVENTS).
      Roughly the same job is to be done for timezones :)
      ed1696f6
    • jan@hundin.mysql.fi's avatar
      Revert error I did. · d8659b27
      jan@hundin.mysql.fi authored
      d8659b27
    • jan@hundin.mysql.fi's avatar
  2. 02 Feb, 2005 2 commits
  3. 01 Feb, 2005 18 commits
  4. 31 Jan, 2005 16 commits