• 's avatar
    Bug #46998 mysqlbinlog can't output BEGIN even if the database is included in a transaction · f4b6aeaf
    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.
    f4b6aeaf
mysqlbinlog.test 14.8 KB