Bug #74617 Timestamp with microseconds not supported in synchronization

• Submitted: 29 Oct 2014 11:42
• Modified: 4 Nov 2014 16:10
• Reporter: Davide Prade
• Status: Verified
• Category: MySQL Workbench: Modeling
• Severity: S2 (Serious)
• Version: 6.2.3, 8.0
• OS: Any
• CPU Architecture: Any
• Tags: microseconds, TIMESTAMP(6)

[29 Oct 2014 11:42] Davide Prade

Description:
In EER diagram the function "Database-->Synchronize with Any Source" doesn't works with "TIMESTAMP(6)" columns.

How to repeat:
Open an EER diagram and click on "Database-->Synchronize with Any Source" menu item.

Select "NEW.sql" as source script file.
Select "OLD.sql" as destination script file.
Select "diff.sql" as ALTER script File.
Generate the ALTER script file with the wizard.

The program generate a wrong CREATE TABLE statement without the microsecond column specifications.

[29 Oct 2014 11:43] Davide Prade

Source script

Attachment: NEW.sql (application/octet-stream, text), 706 bytes.

[29 Oct 2014 11:43] Davide Prade

Destination script

Attachment: OLD.sql (application/octet-stream, text), 400 bytes.

[29 Oct 2014 11:44] Davide Prade

ALTER script

Attachment: diff.sql (application/octet-stream, text), 734 bytes.

[4 Nov 2014 16:10] MySQL Verification Team

Thank you for the bug report.

[27 Oct 2016 11:04] MySQL Verification Team

http://bugs.mysql.com/bug.php?id=83490 marked as duplicate of this one.

[16 Sep 2020 19:33] John E

Test Case:
Implemented schema has a datetime(4) column, while the MSW Model simply has a datetime without microseconds declared.
Upon reverse synchronization, MSW states that it has updated the model successfully.  However, this is not the case.  And thereafter, when synchronizations are attempted, MSW declares the model and the implemented schema to be in synch (although upon inspection, they are not).

[16 Sep 2020 19:36] John E

Forgot to note, the previous test case with datetime(4) non-synchronization is with build MSW 8.0.21 against a 8.0.20R3 Linux distribution MySQL Server.

[30 Apr 2021 13:13] MySQL Verification Team

Bug #103542 marked as duplicate of this one.

[17 Jun 2021 12:15] MySQL Verification Team

Bug #104022 marked as duplicate of this one.

[25 Jun 2021 12:16] MySQL Verification Team

Bug #104094 marked as duplicate of this one.

[26 Jul 2021 13:17] MySQL Verification Team

Bug #104417 marked as duplicate of this one.

[12 Oct 2022 7:08] MySQL Verification Team

Bug #108740 marked as duplicate of this one.

[9 Mar 2023 9:53] MySQL Verification Team

Bug #110304 marked as duplicate of this one.

[17 Apr 2023 7:06] MySQL Verification Team

Bug #110700 marked as duplicate of this one.

[19 May 2023 7:21] MySQL Verification Team

Bug #111078 marked as duplicate of this one.