MySQL Bugs: #101484: Foreign keys are not shown in their tab under a table info.

Bug #101484	Foreign keys are not shown in their tab under a table info.
Submitted:	5 Nov 2020 19:37	Modified:	26 Oct 2021 13:13
Reporter:	Filippo Landi	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S4 (Feature request)
Version:	8.0.22	OS:	Linux (Fedora release 33 Thirty Three x86_64)
Assigned to:		CPU Architecture:	x86
Tags:	WBBugReporter

Description:
----[For better reports, please attach the log file after submitting. You can find it in /home/cippo95/.mysql/workbench/log/wb.log]
Foreign keys are not shown in their tab under a table info.
Trying to refresh in that tab gives: "Unhandled exception:invalid column constraint_name for resultset".

How to repeat:
Foreign keys are not shown in their tab under a table info.
Trying to refresh in that tab gives: "Unhandled exception:invalid column constraint_name for resultset".

Suggested fix:
It should display foreign keys as desired.

wb.log file

Attachment: wb.log (text/x-log), 6.61 KiB.

This is happening for us too.

We have a MySql 8.0.22 database, running in Docker (for development) and natively on linux (for test/production).

We experienced this problem when using Workbench 8.0.19 and were hoping the upgrade to workbench 8.0.22 would address the issue but are sad that it has not.

Looking on the "DDL" tab it clearly shows FK constraints against the table, but as per original poster there is simply a blank "Foreign Keys" tab.

This is happening to me also. I am using 8.0.24.0.

Same issue with 8.0.25

Same issue with v. 8.0.26 build 972499 on Ubuntu 20.04 (64 bits)

Hello Filippo Landi,

Thank you for the bug report.
Imho this is duplicate of Bug #102496, please see Bug #102496.

Regards,
Ashwini Patil

I am using MYSQL workbench version 8.0.28 I am facing the same issue 

"Looking on the "DDL" tab it clearly shows FK constraints against the table, but as per the original poster there is simply a blank "Foreign Keys" tab"

please suggest the solution

The same issue here. I am also using MYSQL workbench version 8.0.28

Still happening in 8.0.31 - blank Foreign keys page, DDL shows multiple foreign key constraints, and error when you hit refresh. Log of error is similar to that in "duplicate" bug.

Still happening in 8.0.32

I am surprised this is something that is still not fixed many versions and nearly two years later. This is an issue for me in Workbench in 8.0.34 running on Linux Mint 21.1 (based on Ubuntu 22.04). The server is 8.0.33 (Homebrew) running on macos13.3.

Note that the foreign keys are displayed fine in Workbench 8.0.34 when the server being viewed is 5.7.21 (Homebrew) but not when it is 8.0.33 (Homebrew).

I used a CASE tool to generate the DDL, so I assume the CASE tool is not following the nameing guidelines for FK. Where can I find the naming guidelines?

modules\sqlide_catalogman_ext.py

Around line 342:

if self.target_version.is_supported_mysql_version_at_least(8, 0, 0)  and type(field) is str:

should be:

if self.target_version.is_supported_mysql_version_at_least(8, 0, 0)  and type(field_obj) is str:

For versions after 8.0 (such as 8.4), in addition to the above, it will also require editing Workbench\utils.py

Around line 209, remove " and self.minorNumber == 0" from:
        if (self.majorNumber == 5 and self.minorNumber in (1, 5, 6, 7)) or (self.majorNumber == 8 and self.minorNumber == 0):

Around line 224, remove " and minor == 0" from:
        if (major == 5 and minor >= 6) or (major == 8 and minor == 0):

i tried the solutions suggested and it didn't work(please note that i'm not a developer so if you can give a step by step guide to solve this problem on my pc)