Bug #38854 | wrong data if SIGNED/UNSIGNED bit doesn't match | ||
---|---|---|---|
Submitted: | 18 Aug 2008 13:15 | Modified: | 18 Aug 2008 18:42 |
Reporter: | Jan Kneschke | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.1.26, 5.1, 6.0 bzr | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[18 Aug 2008 13:15]
Jan Kneschke
[18 Aug 2008 13:17]
Mats Kindahl
Incorrect data is also generated for statement-based replication.
[18 Aug 2008 13:21]
Jan Kneschke
The initial description is missing "SET SESSION binlog_format=row" in the first case to trigger RBR events to be written to the logs.
[18 Aug 2008 18:42]
Sveta Smirnova
Thank you for the report. Verified as described. I think bug here is only inconsistence between statement based and row based repolication. Verified with a bit modified test case: --source include/master-slave.inc --connection master use test; set SQL_LOG_BIN=0; set session binlog_format=row; DROP TABLE IF EXISTS t1; CREATE TABLE t1 (i1 TINYINT SIGNED); --connection slave use test; DROP TABLE IF EXISTS t1; CREATE TABLE t1 (i1 TINYINT UNSIGNED); --connection master use test; set SQL_LOG_BIN=1; SET SESSION binlog_format=row; INSERT INTO t1 VALUES ( -1); SET SESSION binlog_format=statement; INSERT INTO t1 VALUES ( -1); SELECT * FROM t1; --sync_slave_with_master connection slave; SELECT * FROM t1;