Bug #56078 fix the foreign keys tab
Submitted: 17 Aug 2010 23:11 Modified: 9 Oct 2010 3:00
Reporter: Alex Barker Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.26 OS:Linux (Gentoo)
Assigned to: CPU Architecture:Any

[17 Aug 2010 23:11] Alex Barker
Description:
well i typed out a nice long bug report and your awesome bug system gave me an sweet sever not found error so you get the abridged version now. 

your forein keys tab does not work, the index colums do not update when selecting a referencedd table and the apply button tells me there are no changes most of the time but accentually works on occasion

How to repeat:
try using the tab
[17 Aug 2010 23:30] MySQL Verification Team
Thank you for the bug report. Which version are you using?. Please provide the output of Help->System Info. Thanks in advance.
[17 Aug 2010 23:39] Alex Barker
added version and OS information
[17 Aug 2010 23:40] Alex Barker
MySQL Workbench CE for Linux/Unix version 5.2.26
Data Directory: /usr/share/mysql-workbench
Cairo Version: 1.8.10
Rendering Mode: OpenGL is not available on this system, so Native is used for rendering.
OS: Linux 2.6.34-gentoo-r1
CPU: 4x Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz 1600.000 MHz, 7.9 GB RAM
[24 Aug 2010 19:47] Sveta Smirnova
Thank you for the feedback.

we have at least 6 not fixed bugs related to foreign keys: please check if you experience same issue as in following bug #55910, bug #53277, bug #54471, bug #51990, bug #50961 and bug #50751
[24 Aug 2010 22:55] Alex Barker
Its closely related to bug #51990 part 1.  Other issues I experienced were not being able to click the apply button after making changes because for some reason after using the fk dialog changes made to the tables were no longer detected.  This was obviously in the alter table dialog.
[9 Sep 2010 3:00] MySQL Verification Team
Could you please try version 5.2.27. Thanks in advance.
[9 Oct 2010 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".