• Michael Widenius's avatar
    Fix for MDEV-5589: "Discrepancy in binlog on half-failed CREATE OR REPLACE" · c4bb7cd6
    Michael Widenius authored
    Now if CREATE OR REPLACE fails but we have deleted a table already, we will generate a DROP TABLE in the binary log.
    This fixes this issue.
    
    In addition, for a failing CREATE OR REPLACE TABLE ... SELECT we don't generate a log of all the inserted rows, only the DROP TABLE.
    
    I added code for not logging DROP TEMPORARY TABLE for tables where the CREATE TABLE was not logged. This code will be activated in 10.1
    by removing the code protected by DONT_LOG_DROP_OF_TEMPORARY_TABLES.
    
    
    
    
    
    mysql-test/suite/rpl/r/create_or_replace_mix.result:
      More test cases
    mysql-test/suite/rpl/r/create_or_replace_row.result:
      More test cases
    mysql-test/suite/rpl/r/create_or_replace_statement.result:
      More test cases
    mysql-test/suite/rpl/t/create_or_replace.inc:
      More test cases
    sql/log.cc:
      Added binlog_reset_cache() to clear the binary log.
    sql/log.h:
      Added prototype
    sql/sql_insert.cc:
      If CREATE OR REPLACE TABLE ... SELECT fails:
      - Don't log anything if nothing changed
      - If table was deleted, log a DROP TABLE.
      Remember if we table creation of temporary tables was logged.
    sql/sql_table.cc:
      Added log_drop_table()
      Remember if we table creation of temporary tables was logged.
      If CREATE OR REPLACE TABLE ... SELECT fails and a table was deleted, log a DROP TABLE.
    sql/sql_table.h:
      Added prototype
    sql/sql_truncate.cc:
      Remember if we table creation of temporary tables was logged.
    sql/table.h:
      Added table_creation_was_logged
    c4bb7cd6
sql_insert.cc 143 KB