Bug #79012 Workbench modeling - Impossible to set JSON data type

• Submitted: 28 Oct 2015 21:54
• Modified: 8 Dec 2015 1:54
• Reporter: Luca Anceschi
• Status: Closed
• Category: MySQL Workbench: Modeling
• Severity: S2 (Serious)
• Version: 6.3.5
• OS: Ubuntu
• CPU Architecture: Any

[28 Oct 2015 21:54] Luca Anceschi

Description:
Hi,

it's impossible to set JSON data type in workbench table modeling.

Best regards,
Luca

How to repeat:
Go to Preferences > Modeling > MySQL > DEfault MySQL Target Version and set it to 5.7 and hit ok.

Create a new model and a new table. Add an dummy autoincrement PK field of type INT.

Create an additional field and I'm not able to set the datatype to JSON even if I can see and select from the drop down menu. I can select it altough the cell revert to the previous data type as soon as the cell lost input focus.

I made a try setting the field individual collation to utf8mb4 - utf8mb4_bin. Same result. I cannot set the data type to JSON. As soon as the data type cell lost input focus it reverts back to VARCHAR(45) for example.

Best regards,
Luca

[28 Oct 2015 21:55] Luca Anceschi

Here you'll find a screenshot

Attachment: Screenshot from 2015-10-28 22:36:10.png (image/png, text), 32.96 KiB.

[29 Oct 2015 5:05] MySQL Verification Team

Hello Luca Anceschi,

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

Thanks,
Umesh

[29 Oct 2015 5:07] MySQL Verification Team

Screenshot..

Attachment: 79012.png (image/png, text), 73.73 KiB.

[8 Dec 2015 1:54] Philip Olson

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.3.6 release, and here's the changelog entry:

The modeling table editor did not list the JSON data type in the dropdown
select list, nor did it accept it manually. Importing a JSON column from a
live database worked, but creating/assigning the JSON type in the editor
was not possible.

Thank you for the bug report.

[11 Jul 2016 8:54] Matthias Litsche

Still broken with existing models/diagrams.
Tried version 6.3.6 & 6.3.7. 

log:
[WRN][  TableEditorBE]: JSON is not a valid column type

Workaround:
Create a new model and include the old model(EER Diagram). File->Include Model...