Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 5.3.12, 5.5.37, 10.0.10
-
Fix Version/s: 10.1
-
Component/s: None
-
Labels: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.
Gliffy Diagrams
Attachments
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
one possible solution — use MySQL-5.6 compatible on-disk format for temporal columns by default.