[MDEV-5297] TIME(0), TIMESTAMP(0) and DATETIME(0) are self-incompatible during replication (upstream) Created: 2013-11-15  Updated: 2013-12-06  Resolved: 2013-12-06

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.5
Fix Version/s: 10.0.7

Type: Bug Priority: Minor
Reporter: Alexander Barkov Assignee: Alexander Barkov
Resolution: Fixed Votes: 0
Labels: upstream


 Description   

The upstream bug http://bugs.mysql.com/bug.php?id=70124
is repeatable with MariaDB-10.0.5.

How-to-repeat:

  • Install and start two instances:
    MySQL-5.6 for master, and MariaDB-10.0.5 for slave.
    Do not start replication at this point.
  • On MySQL-5.6 master: create a table with non-fractional temporal fields:

    CREATE TABLE t1 (a time(0), b datetime(0), c timestamp(0)) engine=myisam;

  • On MariaDB-10.0.5 slave: create a table with the same structure:
  • "Upgrade" master: stop MySQL-5.6 and start MariaDB-10.0.5 on top
    of the MySQL-5.6 data directory.
  • Configure and start row-based replication between master and slave.
  • Start replication
  • Insert some data on master:

    INSERT INTO t1 VALUES ('00:00:02','2001-01-01 00:00:02','2001-01-01 00:00:02');

Slave will fail with this error:

SHOW SLAVE STATUS;
...
Last_Error	Column 0 of table 'test.t1' cannot be converted from type 'time' to type 'time'



 Comments   
Comment by Alexander Barkov [ 2013-12-06 ]

Fixed in 10.0.

Generated at Thu Feb 08 07:03:11 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.