Bug #88880 Synchronize error when using JSON format columns

• Submitted: 12 Dec 2017 16:23
• Modified: 13 Dec 2017 12:06
• Reporter: Davis Jaunzems
• Status: Duplicate
• Category: MySQL Workbench
• Severity: S1 (Critical)
• Version: 6.3.10
• OS: Linux (Ubuntu 16.04 x86_64)
• CPU Architecture: Any
• Tags: WBBugReporter

[12 Dec 2017 16:23] Davis Jaunzems

Description:
When synchronizing the EER model workbench doesn't remember what tables it created when table model contains a JSON format column. Tables and views are created, but on every synchronization tables with JSON columns are treated as non-existing and a SQL for creating a table is generated, e.g., "CREATE TABLE IF NOT EXISTS". When the column format is changed to Text then workbench remembers the table and doesn't try to re-create it.

Issue is on MySQL Community Server 5.7.19, 5.7.20 and 8.0.3-rc.

How to repeat:
1) Create a model in EER where one or more columns are JOSN type
2) Synchronize
3) Check if final the final generated SQL contains "CREATE TABLE IF NOT EXISTS" even after 2 or more synchronizations.

[12 Dec 2017 16:55] MySQL Verification Team

Thank you for the bug report. Please provide the model test case file (use Files tab for). Thanks in advance.

[13 Dec 2017 7:51] Davis Jaunzems

Model, description and few pictures.

Attachment: mysql-bug-data-88880.zip (application/zip, text), 247.69 KiB.

[13 Dec 2017 7:53] Davis Jaunzems

Added extra wb.log file

Attachment: mysql-bug-data-88880.zip (application/zip, text), 249.60 KiB.

[13 Dec 2017 11:39] Chiranjeevi Battula

Hello Davis Jaunzems,

Thank you for the bug report.
This is most likely duplicate of Bug #85648, please see Bug #85648

Thanks,
Chiranjeevi.

[13 Dec 2017 12:06] Davis Jaunzems

Thank you Chiranjeevi Battula, it looks like duplicate scenario indeed.