[
https://issues.apache.org/jira/browse/DDLUTILS-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Dudziak resolved DDLUTILS-75.
------------------------------------
Resolution: Fixed
onUpdate and onDelete are in the XML schema, and are also read back from the DB.
> Add support for "On Delete" and "On Update" in schema XML for foreign keys
> --------------------------------------------------------------------------
>
> Key: DDLUTILS-75
> URL: https://issues.apache.org/jira/browse/DDLUTILS-75
> Project: DdlUtils
> Issue Type: Improvement
> Components: Core (No specific database)
> Environment: Oracle 10g Express Edition
> Windows XP
> Java 1.5.0
> Ant 1.6.5
> Reporter: Guy Davis
> Assignee: Thomas Dudziak
> Priority: Critical
> Fix For: 1.1
>
> Attachments: delete_cascade.patch, delete_cascade2.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
