• unknown's avatar
    Bug #46998 mysqlbinlog can't output BEGIN even if the database is included in a transaction · 508527a9
    unknown authored
    The 'BEGIN/COMMIT/ROLLBACK' log event could be filtered out if the
    database is not selected by --database option of mysqlbinlog command.
    This can result in problem if there are some statements in the
    transaction are not filtered out.
    
    To fix the problem, mysqlbinlog will output 'BEGIN/ROLLBACK/COMMIT' 
    in regardless of the database filtering rules.
    
    client/mysqlbinlog.cc:
      Skip the database check for BEGIN/COMMIT/ROLLBACK log events.
    mysql-test/r/mysqlbinlog.result:
      Test result for bug#46998
    mysql-test/suite/binlog/t/binlog_row_mysqlbinlog_db_filter.test:
      The test case is updated duo to the patch of bug#46998
    mysql-test/t/mysqlbinlog.test:
      Added test to verify if the 'BEGIN', 'COMMIT' and 'ROLLBACK' are output
      in regardless of database filtering
    508527a9
mysqlbinlog.result 19.6 KB