Bug #82378 | Table editor cannot create foreign key if referenced table has JSON column | ||
---|---|---|---|
Submitted: | 29 Jul 2016 0:38 | Modified: | 29 Jul 2016 4:47 |
Reporter: | Matt Liston | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 6.3.7 | OS: | Windows |
Assigned to: | CPU Architecture: | Any |
[29 Jul 2016 0:38]
Matt Liston
[29 Jul 2016 0:39]
Matt Liston
Error Screenshot
Attachment: fk_test.png (image/png, text), 21.57 KiB.
[29 Jul 2016 4:47]
MySQL Verification Team
Hello Matt Liston, Thank you for the report and test case. Observed this with WB 6.3.7 on Win7. Thanks, Umesh
[16 Jul 2017 21:38]
Andrew Martin
Is this a limitation on MySQL with JSON? still happening in 6.3.9 about 1 year later.
[15 Nov 2018 20:48]
carlos jimenez
Hi, this bug still happening in Mysql Workbench 8.0.11 2 years later, ¿Someone has any comment about this? Thanks
[25 Jan 2019 18:46]
Justin Levene
I have found this bug as well. I have to script foreign keys as MySQL Workbench can't do them due to this bug. It doesn't seem to be tables with JSON fields in them (where the foreign key is being added), rather linking to a table with a JSON field in it.
[19 Apr 2021 10:41]
Rui Rodrigues
In version 8.023 remains the problem. Only manually I can create the fk