mirror of
https://github.com/MariaDB/server.git
synced 2025-01-22 23:04:20 +01:00
e3708c231e
TRUNCATE TABLE fails to replicate when stmt-based binlogging is not supported. There were two separate problems with the code, both of which are fixed with this patch: 1. An error was printed by InnoDB for TRUNCATE TABLE in statement mode when the in isolation levels READ COMMITTED and READ UNCOMMITTED since InnoDB does permit statement-based replication for DML statements. However, the TRUNCATE TABLE is not transactional, but is a DDL, and should therefore be allowed to be replicated as a statement. 2. The statement was not logged in mixed mode because of the error above, but the error was not reported to the client. This patch fixes the problem by treating TRUNCATE TABLE a DDL, that is, it is always logged as a statement and not reporting an error from InnoDB for TRUNCATE TABLE.
16 lines
472 B
Text
16 lines
472 B
Text
#
|
|
# Copyright 2006 MySQL. All rights reserved.
|
|
#
|
|
# Test to check for the different version of truncating a table.
|
|
# The statements are "TRUNCATE tbl" and "DELETE FROM tbl". We check
|
|
# the behaviour of each possible value for BINLOG_FORMAT.
|
|
#
|
|
# Author(s): Mats Kindahl
|
|
|
|
--source include/master-slave.inc
|
|
|
|
let $trunc_stmt = TRUNCATE TABLE;
|
|
--source extra/rpl_tests/rpl_truncate_helper.test
|
|
|
|
let $trunc_stmt = DELETE FROM;
|
|
--source extra/rpl_tests/rpl_truncate_helper.test
|