Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
5.3.12, 5.5.37, 10.0.10
-
None
Description
Row based replication of the TIME(N), DATETIME(N) and TIMESTAMP(N)
data types does not store column metadata into the binary log, so
slave does not have any information about the precision of the column on
master. Slave can only assume that the precision is exactly the same
on master and on slave.
This puts some limitations. Examples when RBR does not work:
- From TIME(N) to TIME(M), for N!=M
- From TIME(N) to another data type, e.g. VARCHAR or DECIMAL.
- From TIME(N) in a MariaDB master to TIME(N) in a MySQL56 slave.
Attachments
Issue Links
- duplicates
-
MDEV-5528 Command line variable to choose MariaDB-5.3 vs MySQL-5.6 temporal data formats
- Closed
-
MDEV-10746 Replicate Data from 10.0 -> 10.1 (Corrupted replication event was detected )
- Closed
-
MDEV-12744 Corrupted replication event was detected. Not printing the value
- Closed
- includes
-
MDEV-6389 DATETIME w/ transportable tablespaces from MySQL 5.6 to MariaDB 10.0 gives "precise type mismatch" error.
- Open
- is blocked by
-
MDEV-5528 Command line variable to choose MariaDB-5.3 vs MySQL-5.6 temporal data formats
- Closed
- relates to
-
MDEV-19906 Show internal type for TIMESTAMP, DATETIME, and TIME columns
- Closed
-
MDEV-9567 mysqlbinlog fails to read binlog event which inserts timestamp with wrong number of microseconds
- Closed