• guilhem@mysql.com's avatar
    Fix for BUG#6522 "Replication fails due to a rolled back transaction in the binlog" · 0c4363b6
    guilhem@mysql.com authored
    When we are writing a transaction to the binlog, we log BEGIN/COMMIT with zero error code.
    Example: all statements of trans succeeded, connection lost and so implicit rollback:
    we don't want ER_NET* errors to be logged in the BEGIN/ROLLBACK events, while statement
    events have 0. If there was really a serious error code, it's already in the statement events.
    0c4363b6
sql_table.cc 65.3 KB