MySQL Bugs: #50749: Fk On Delete Shows empty when editing tables

Bug #50749	Fk On Delete Shows empty when editing tables
Submitted:	29 Jan 2010 20:40	Modified:	28 Feb 2010 21:20
Reporter:	Martin Pirringer	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	5.2.15	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	delete, foreign key, table edit

Description:
myproject.mvb initially created with 5.1.18 When loaded in 5.2.15 All foreign keys "Delete" showed empty in the Model and also when doing "Alter Table" from any other place like the sql editor by right clicking on the Table. Sql Query Browser 5.0 and Mysql Administrator show the proper "Delete Restrict" setting for the table. Subsequent setting or not setting of the "Delete Restrict" FK in the 5.2.15 Modeler and then Syncing the DB will not generate any SQL code. 

How to repeat:
Create A table with Workbench 5.1 or Mysqladmin and Set a Foreign key with 
"Delete Restrict" Feature

Open Workbench 5.2.15 go to SQL editor Right click table
click "Alter Table"
click foreign key tab
highlight th foreign key.

Update will show the proper feature (like cascad)
Delete will show Blank.

Suggested fix:
Properly read the Foreign Key Delete setting

for InnoDB tables RESTRICT is the default value for on update/delete. so if you create a table having "on delete restrict" defined, and then puling the DDL for the table back from server you wont get any "on delete restrict" in the statement either. This is the reason WB doesn't display the on delete restrict when loading the live-editor.
For the modelling part, i could not reproduce the problem (except for the case that i had created a model by reverse engineering a database). Could you maybe provide your model which shows the restrict-parameters in 5.1.18 but not in 5.2?

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".