Bug #12443 Timestamp incorrectly replicated with rbr.
Submitted: 8 Aug 2005 18:17 Modified: 18 Nov 2005 14:04
Reporter: Jonathan Miller Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S1 (Critical)
Version:5.0-wl1012 OS:Linux (Linux)
Assigned to: Lars Thalmann CPU Architecture:Any

[8 Aug 2005 18:17] Jonathan Miller
Description:
Take the following test case for example: 

master> set time_zone='UTC';
Query OK, 0 rows affected (0.00 sec)

slave> set time_zone='UTC';
Query OK, 0 rows affected (0.00 sec)

slave> start slave;
Query OK, 0 rows affected (0.01 sec)

master> create table t1 (t timestamp, n int not null auto_increment, PRIMARY KEY(n));
Query OK, 0 rows affected (0.00 sec)

master> insert into t1 values ('20050101000000', NULL), ('20050611093902',NULL);
Query OK, 2 rows affected (0.01 sec)
Records: 2  Duplicates: 0  Warnings: 0

master> insert into t1 values ('20040101000000',NULL), ('20040611093902',NULL);
Query OK, 2 rows affected (0.00 sec)
Records: 2  Duplicates: 0  Warnings: 0

master> select * from t1;
+---------------------+---+
| t                   | n |
+---------------------+---+
| 2005-01-01 00:00:00 | 1 |
| 2005-06-11 09:39:02 | 2 |
| 2004-01-01 00:00:00 | 3 |
| 2004-06-11 09:39:02 | 4 |
+---------------------+---+
4 rows in set (0.00 sec)

master> show create table t1;
+-------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Table | Create Table                 |
+-------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| t1    | CREATE TABLE `t1` (
  `t` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
    `n` int(11) NOT NULL auto_increment,
      PRIMARY KEY  (`n`)
      ) ENGINE=MyISAM DEFAULT CHARSET=latin1 |
      +-------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
      1 row in set (0.00 sec)

slave> show tables;
+----------------+
| Tables_in_test |
+----------------+
| t1             |
+----------------+
1 row in set (0.00 sec)

slave> show create table t1;
+-------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Table | Create Table                                 |
+-------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| t1    | CREATE TABLE `t1` (
  `t` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
    `n` int(11) NOT NULL auto_increment,
      PRIMARY KEY  (`n`)
      ) ENGINE=MyISAM DEFAULT CHARSET=latin1 |
      +-------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
      1 row in set (0.00 sec)

slave> select * from t1;
      +---------------------+---+
      | t                   | n |
      +---------------------+---+
      | 2005-08-08 18:02:24 | 1 |
      | 2005-08-08 18:02:24 | 2 |
      | 2005-08-08 18:02:24 | 3 |
      | 2005-08-08 18:02:24 | 4 |
      +---------------------+---+
      4 rows in set (0.00 sec)

***********************************************
This can be seen throughout the rpl_timezone.test. I have created one called rpl_rpw_timezone.test with PK so that the data replicates and have placed it into mysql-5.0-wl1012:/mysql-test/suite/invest/t/

How to repeat:
see above:
[18 Nov 2005 14:04] Lars Thalmann
Fixed by Guilhems patch