• Mats Kindahl's avatar
    Bug #34707: Row based replication: slave creates table within wrong database · dcd050c5
    Mats Kindahl authored
    The failure was caused by executing a CREATE-SELECT statement that creates a
    table in another database than the current one. In row-based logging, the
    CREATE statement was written to the binary log without the database, hence
    creating the table in the wrong database, causing the following inserts to
    fail since the table didn't exist in the given database.
    
    Fixed the bug by adding a parameter to store_create_info() that will make
    the function print the database name before the table name and used that
    in the calls that write the CREATE statement to the binary log. The database
    name is only printed if it is different than the currently selected database.
    
    The output of SHOW CREATE TABLE has not changed and is still printed without
    the database name.
    
    mysql-test/suite/rpl/t/rpl_row_create_table.test:
      Added test to check that CREATE-SELECT into another database than the
      current one replicates.
    sql/sql_insert.cc:
      Adding parameter to calls to store_create_info().
    sql/sql_show.cc:
      Adding parameter to calls to store_create_info().
      
      Extending store_create_info() with parameter 'show_database' that will cause
      the database to be written before the table name.
    sql/sql_show.h:
      Adding parameter to call to store_create_info() to tell if the database should be shown or not.
    sql/sql_table.cc:
      Adding parameter to calls to store_create_info().
    dcd050c5
sql_insert.cc 123 KB