• unknown's avatar
    Bug#20396 Bin Log does not get DELIMETER cmd - Recover StoredProc fails · 36c7cfd7
    unknown authored
    Problem: when loading mysqlbinlog dumps, CREATE PROCEDURE having semicolons
    in their bodies failed.
    Fix: Using safe delimiter "/*!*/;" to dump log entries.
    
    
    client/mysqlbinlog.cc:
      - Adding PRINT_EVENT_INFO argument to dump_xxx_log_entries()
      - Setting delimiter to "/*!*/;" before calling dump functions
    mysql-test/r/ctype_ucs_binlog.result:
      Fixing test results
    mysql-test/r/mix_innodb_myisam_binlog.result:
      Fixing test results
    mysql-test/r/mysqlbinlog.result:
      Fixing test results
      Adding test case
    mysql-test/r/mysqlbinlog2.result:
      Fixing test results
    mysql-test/r/rpl_charset.result:
      Fixing test results
    mysql-test/r/rpl_timezone.result:
      Fixing test results
    mysql-test/r/user_var-binlog.result:
      Fixing test results
    mysql-test/t/mix_innodb_myisam_binlog.test:
      Fixing LIKE expression
    mysql-test/t/mysqlbinlog.test:
      Adding test case
    sql/log_event.cc:
      Using print_event_info->delimiter instead of
      hard-coded semicolon as a query end marker.
    sql/log_event.h:
      Adding new member to store delimiter.
    36c7cfd7
mysqlbinlog.result 8.37 KB