Bug #45393 Default referential integrity constraints not set for new tables
Submitted: 9 Jun 2009 9:43 Modified: 10 Aug 2009 13:31
Reporter: Karsten Wutzke Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.1.12, 5.2.1alpha OS:Any
Assigned to: Sergei Tkachenko CPU Architecture:Any
Tags: CHECKED, new tables, Options, referential integrity constraints

[9 Jun 2009 9:43] Karsten Wutzke 
Description:
Default referential integrity constraints are not set for new tables

How to repeat:
Go to "Tools" -> "Options..." -> "Model" tab, change the default foreign key constraints to CASCADE. Press OK and close dialog.

Create two tables and connect them via a relationship (e.g. 1:1). Edit the table that references the other. Click on "Foreign Key" tab below, highlight the foreign key and look to the right.

Bogus.
[9 Jun 2009 9:48] Valeriy Kravchuk 
Thank you for the problem report. Verified just as described.
[29 Jul 2009 13:38] Alfredo Kojima 
Bug #45239 marked as duplicate of this
[6 Aug 2009 17:57] Johannes Taxacher 
fix confirmed, will be in 5.1.17
[10 Aug 2009 13:31] Tony Bedford 
An entry was added to the 5.1.17 changelog:

The settings for ON UPDATE and ON DELETE in Foreign Key/Relationship Defaults set in the Model tab of Tools, Preferences, were not taken into account when new tables and relationships were created.