Mailing-List: contact ddlutils-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ddlutils-dev@db.apache.org
Message-ID: <26331007.1152770972278.JavaMail.jira@brutus>
Date: Thu, 13 Jul 2006 06:09:32 +0000 (GMT+00:00)
From: "Thomas Dudziak (JIRA)" <jira@apache.org>
To: ddlutils-dev@db.apache.org
Subject: [jira] Updated: (DDLUTILS-75) Add support for "On Delete" and "On
 Update" in schema XML for foreign keys
In-Reply-To: <1513138966.1140577720290.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DDLUTILS-75?page=all ]

Thomas Dudziak updated DDLUTILS-75:
-----------------------------------

    Fix Version: 1.1

> Add support for "On Delete" and "On Update" in schema XML for foreign keys
> --------------------------------------------------------------------------
>
>          Key: DDLUTILS-75
>          URL: http://issues.apache.org/jira/browse/DDLUTILS-75
>      Project: DdlUtils
>         Type: Improvement

>  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
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira