[DDLUTILS-75] Add support for "On Delete" and "On Update" in schema XML for foreign keys

• Type: Improvement
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.1
• Component/s: Core (No specific database)
• Environment: Oracle 10g Express Edition; Windows XP; Java 1.5.0; Ant 1.6.5
• Assignee: Thomas Dudziak
• Reporter: Guy Davis
• Created: 22/Feb/06 12:07
• Updated: 03/Nov/08 22:01
• Resolved: 03/Nov/08 22:01

Description

Currently, when dumping the schema from a live database to XML, the 'on delete' and 'on update' rules for foreign keys are ignored. As shown in the DTD for database.dtd (below), the attributes onDelete and onUpdate should translate into "on delete cascade" for example in the target SQL.

<!ELEMENT foreign-key (reference+)>
<!ATTLIST foreign-key
foreignTable CDATA #REQUIRED
name CDATA #IMPLIED
onUpdate (cascade|setnull|restrict|none) "none"
onDelete (cascade|setnull|restrict|none) "none"
>

If the dump (DatabaseToDdl) is modified to write these attributes out, then the schema load (DdlToDatabase) needs to handle them and set the correct behavior on the foreign key creation.

Issue Links

• incorporates: DDLUTILS-200 CloneHelper not cloning onDelete and onCascade for ForeignKeys
• is duplicated by: DDLUTILS-82 FOREIGN KEY .... ON UPDATE .... ON DELETE ...
• relates to: DDLUTILS-82 FOREIGN KEY .... ON UPDATE .... ON DELETE ...