search

bigcy / tungsten-replicator

Automatically exported from code.google.com/p/tungsten-replicator
0 stars 0 forks source link

TIME column microseconds are not replicated correctly in RBR #681

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1. start replicator with MySQL 5.6
2. enable row based replication
3. replicate some TIME columns with various depth of microseconds

use test;

drop table if exists timetest;
create table timetest (id int not null primary key,
    t0 time,
    t1 time(1),
    t2 time(2),
    t3 time (3),
    t4 time(4),
    t5 time(5),
    t6 time(6)
);

set binlog_format=row;

insert into timetest values (1,
    '10:10:10',
    '10:10:10.1',
    '10:10:10.01',
    '10:10:10.012',
    '10:10:10.0123',
    '10:10:10.01234',
    '10:10:10.012345' );

What is the expected output?

master and slave have the same contents

What do you see instead?

some decimals are not replicated correctly.

MASTER:

1
10:10:10
10:10:10.1
10:10:10.01
10:10:10.012
10:10:10.0123
10:10:10.01234
10:10:10.012345

1
10:10:10
10:10:10.0          <---
10:10:10.00        <---
10:10:10.000      <---
10:10:10.0123
10:10:10.01234
10:10:10.012345

What is the possible cause?

N/A

What is the proposed solution?

N/A

Additional information

Original issue reported on code.google.com by g.maxia on 23 Aug 2013 at 9:23

GoogleCodeExporter commented 9 years ago

Original comment by linas.vi...@continuent.com on 24 Aug 2013 at 7:16

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r1619.

Original comment by stephane...@continuent.com on 24 Aug 2013 at 10:36

GoogleCodeExporter commented 9 years ago 
All issues should pass Documenting state before Fixed.

Original comment by linas.vi...@continuent.com on 25 Aug 2013 at 7:31

GoogleCodeExporter commented 9 years ago

Original comment by linas.vi...@continuent.com on 25 Aug 2013 at 7:41

GoogleCodeExporter commented 9 years ago 
This is a MySQL 5.6 support bug, so this is more a new bug than a regression. 
Time did not have microseconds previously.

Original comment by linas.vi...@continuent.com on 25 Aug 2013 at 9:16

GoogleCodeExporter commented 9 years ago 
This issue is fixed. Build 2.1.2-23 passes the test

Original comment by g.maxia on 26 Aug 2013 at 6:24

GoogleCodeExporter commented 9 years ago 
An entry has been added to the 2.1.2 release notes.

Original comment by mc.br...@continuent.com on 28 Aug 2013 at 11:45