MySQL Bugs: #47268: On creating foreign keys, selecting referenced column doesnt work

Bug #47268	On creating foreign keys, selecting referenced column doesnt work
Submitted:	11 Sep 2009 9:41	Modified:	14 Sep 2009 14:39
Reporter:	Emil Emilsson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.1.18	OS:	Windows (XP Sp2)
Assigned to:		CPU Architecture:	Any
Tags:	foreign keys, referencing column

Description:
when adding foreign keys to a table creating the foreign key and selecting the referenced table works.

But selecting the referenced column by clicking checkbox besides the reference table to select the referenced colun doesnt work so the dropdown box isnt populated.

I tried closing the program and running it again.

It used to work but somehow doesnt work anymore

How to repeat:
select any table, select "edit table" 
select foreign keys tab

type in the name of the foreign key , select a referenced table
and when you click the checkbox it doesnt get checked that properties part of the page just flickers.

Suggested fix:
obviously stop flicking and allow the box to be checked :)

What exact iversion, 5.1.x do you use? I can not repeat this with latest, 5.1.18, on XP.

I added my mwb file that is the cause of the problem

if you do properties on the researchfund_subcategory table and try to click the checkbox infront of the colum to reference it doesnt get checked.

if I add a new table its fine in that table.

What table should I select as "Referenced table" while trying to add new foreign key to that Reseachfund_Main table? When no table is selected, indeed, you can not check columns, but this is reasonable IMHO - they have nothing to refer to.

I rightclick "researchfund_subcategory2 table

edit that and select foreign keys

there are two "foreign key name" and "Referenced table" i cannot select a column to be the referenced column

fkResearchFundMain for example.

Verified just as described in your last comment. Sorry, used wrong table by mistake...

Hi Emil,

this issue came up in your model because we tightened the checks on datatypes for columns connected in a FK. in your model you've got IN(11) in the table you wanted to create the FKs on, and INT as datatype for the referenced key-columns.
So its actually expected behavior, but we have to improve the feedback for the user on that so that its more obvious why WB refuses to let you link the two columns.

Ok, I didnt realise that I had int(11) in the referenced table.
I agree that an informative error message should be shown.

When I changed that I managed to select those references just fine.

I sometimes managed to get an error message, like a crash message when messing around with that but it didnt crash the whole program. If I manage to get that message again I will paste it into a new bug report.

But thank you for solving that problem :)