Bug #56907 | Cannot create foreign key relationship using Table Editor | ||
---|---|---|---|
Submitted: | 21 Sep 2010 19:47 | Modified: | 5 Dec 2010 17:28 |
Reporter: | Moua Xiong | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S1 (Critical) |
Version: | 5.2.27, 5.2.28 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | foreign key, unable to add to table |
[21 Sep 2010 19:47]
Moua Xiong
[22 Sep 2010 0:37]
MySQL Verification Team
Could you please try version 5.2.28. Thanks in advance.
[22 Sep 2010 12:59]
Moua Xiong
I upgraded to version 5.2.28 but that didn't help either. I was able to go back into the table and see the FKs I added via scripting but then when I unchecked the checkbox under the column, I couldn't add it back in anymore. At this point, I'm not sure what's causing that to happen. Any additional help would be greatly appreciated as I'm really excited about the new workbench tool so I'd like it to work correctly. Please let me know what else I could try. Thanks.
[23 Sep 2010 12:37]
Moua Xiong
Please let me know if you have any other suggestions.
[27 Sep 2010 15:02]
Alfredo Kojima
What are the exact types of the columns?
[27 Sep 2010 16:13]
Moua Xiong
The columns are a primary key in the main table and then an integer in the join table.
[5 Nov 2010 17:28]
Johannes Taxacher
sounds like a type mismatch. if you create a table with a PK column typed as "INT", this column is created in server as INT(11) ... when you then create the second table and use "INT" again for the column you're about to link to the first table, WB refuses to wire "INT" and "INT(11)" ... as a workaround, you can explicitly specify "INT(11)" as column type for the FK col in 2nd table - that should get WB to allow hooking those columns up.
[5 Nov 2010 17:30]
Johannes Taxacher
if thats the problem you're facing, then this report is a duplicate of Bug #56024.
[6 Dec 2010 0: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".