Bug #66384 | Can't unckeck column in foreign keys | ||
---|---|---|---|
Submitted: | 14 Aug 2012 17:04 | Modified: | 17 Aug 2012 12:51 |
Reporter: | none none | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Workbench | Severity: | S2 (Serious) |
Version: | 5.2.42 | OS: | Windows (Microsoft Windows 7 Service Pack 1 (build 7601), 64-bit) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[14 Aug 2012 17:04]
none none
[15 Aug 2012 18:56]
Rafael Antonio Bedoy Torres
Hello, where are you creating the table, on SQL Editor section or on Model section? Can you please add a step by step list of what you did? Thanks!
[15 Aug 2012 21:51]
none none
It's in model section. I created table, define columns and click to tab "Foreign keys" than i write name of key, choose table, check box by column and than it's opened select of columns, i guess that this bad behavior cause table select doesn't do this. And every time when i want uncheck column so i can't cause is probably again checked and opened select for column choose. I hope you understand me, english doesn't my native language... :) model has 31+ tables and 5+ diagrams...
[16 Aug 2012 15:48]
Evert Harmeling
I have the same issue it's best explained if you want to create a many-to-many table for example `user_organization` which includes `user_id` and `organization_id`. When you want to define the foreign keys it's no problem for `user_id` as it seems to go the top possible related column. But when you try to create a foreign key for `organization_id` it's wants to also check the `user_id` column as a related column which then CAN'T be unchecked. It looks like the select box in the 'Referenced Column' has no 'null' value and therefor can't be deselected which results in a checkbox which always gets checked. Possible fix: Probably add a null value to the select box...
[16 Aug 2012 16:04]
Evert Harmeling
Workbench screenshot
Attachment: workbench_bug_66384.PNG (image/png, text), 23.66 KiB.
[17 Aug 2012 8:49]
Evert Harmeling
Temporary workaround: Changing the order of the columns when defining the foreign keys, so that the key you want to relate to is on top of the list everytime you want the define a foreign key.
[17 Aug 2012 12:51]
Alfredo Kojima
Duplicate of bug #66171