Bug #77764 data modeler does not retrieve precision for "datetime" datatypes at reverse eng

• Submitted: 17 Jul 2015 15:05
• Modified: 22 Jul 2015 8:27
• Reporter: Denes Berger
• Status: Verified
• Category: MySQL Workbench: Modeling
• Severity: S3 (Non-critical)
• Version: 6.3.4
• OS: Windows (Microsoft Windows 7 Enterprise Service Pack 1)
• CPU Architecture: Any
• Tags: WBBugReporter

[17 Jul 2015 15:05] Denes Berger

Description:
data modeler does not retrieve precision for "datetime" datatypes at reverse engineering

How to repeat:
- create a table in a schema that contains a datetime(6) field
- create new model and start reverse engineering
- select the schema selected in first point for reverse engineering
- after reverse engineering wizard is done, select the table and double click on it
- check column types. precision is lost, i.e. it shows datetime

Suggested fix:
include precision for all datatypes in reverse engineering

[22 Jul 2015 8:27] MySQL Verification Team

Hello Denes,

Thank you for the report.
Observed this with WB 6.3.4 on Win7.

Thanks,
Umesh

[22 Jul 2015 8:28] MySQL Verification Team

Screenshot..

Attachment: 77764.png (image/png, text), 33.81 KiB.

[12 Apr 2023 7:38] Fredric Johansson

This is still an issue with v8.0.30.
Additionally if an column includes CURRENT_TIMESTAMP(3) this will cause an error in the import and the table won't be imported to the model. Synchronize will not error out on this but the precision on the type is still not imported.