MySQL Bugs: #36453: Problem with FOREIGN keys

Bug #36453	Problem with FOREIGN keys
Submitted:	1 May 2008 13:41	Modified:	22 Aug 2008 16:00
Reporter:	Sergey Romanov	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.0.21	OS:	Windows (XP SP2)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any

Description:
After I have changed latest RC SE version to OSS I have found that all FOREIGN keys, created in SE version have INDEX type, not FOREIGN (in Indexes tab) and I can not change type to FOREIGN.
After export to sql file I can see that CREATE command is correct, i.e. with CONSTRAIN, FOREIGN KEY and etc.
When I create new FOREIGN key (in diagram with 'Place a Relationship Using Existing Columns') then all is ok and I can see FOREIGN key type. 
Relations in SE was created with 'Place a New 1:n Identifying Relationship'.

How to repeat:
Try to open file with foreign keys created with SE.

Suggested fix:
WB should show correct index type.

Thank you for the bug report.

Please upload an example model file which shows this problem.

I've changed the editor so that you can manually force an index to be of type FOREIGN.
This should be used for workaround purposes only.

as mentioned by developer, only use this for correction-purposes as Workbench sets that indextype automatically. This is only for models, created with older versions of wb that didn't support the FOREIGN type. Indexes set to FOREIGN cannot be changed back manually to INDEX (except by using the undo feature).

Did this change make it into 5.0.22?

yes, fix was included in 5.0.22

An entry was added to the 5.0.22 changelog:

When opening a model created with an earlier version of Workbench, the Indexes tab displayed indexes of type FOREIGN as type INDEX, and it was not possible to change them back to FOREIGN.