Bug #82081 json type cannot be dealt well in synchronize
Submitted: 1 Jul 2016 9:33 Modified: 17 Nov 2017 6:28
Reporter: panda small Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:6.3.10 OS:Any
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[1 Jul 2016 9:33] panda small 
Description:
If a table has a json type column, this table cannot be synchronized with the MYSQL Server. I must drop this table first if I want to synchronize the model.

How to repeat:
Create a table with a json column in server, and reverse it to a model. Then when you synchronize the model to the server, you can not find the table in the server. It require you to recreate this table.
[1 Jul 2016 11:04] MySQL Verification Team 
Hello!

Thank you for the report.
Verified as described with WB 6.3.7 on Win7.

Thanks,
Umesh
[16 Mar 2017 6:54] W Ding 
Is there a fix or workaround? I'm still seeing it with WB 6.3.8 on win7.
[18 Mar 2017 11:30] Jakub Caban 
Problem persists also in 6.3.9. It makes working with JSON tables via Model Editor nearly impossible - every change has to be applied manually to target databases.

Could any of the developers at lease give us a hint at where in the code base to look for? Maybe we'd be able to come with a patch.
[28 Aug 2017 10:40] MySQL Verification Team 
Bug #87561 marked as duplicate of this
[14 Oct 2017 19:50] William Panec 
Is there any updates on this?
[17 Nov 2017 3:20] Roger Lin 
Problem persists also in 6.3.10.
[17 Nov 2017 6:28] panda small 
The more json type of columns I use, the more inconvenient usage I got. As mysql support so great for json, when can we use MySQL Workbench so convenient too?
[13 Mar 2018 7:14] Risheng Hu 
Is there any plan to fix this?