db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: [jira] Updated: (DERBY-338) Move checks for referential constraints from DDL execution time to DML execution time
Date Tue, 07 Jun 2005 16:49:17 GMT
Jack Klebanoff (JIRA) wrote:
>      [ http://issues.apache.org/jira/browse/DERBY-338?page=all ]
> Jack Klebanoff updated DERBY-338:
> ---------------------------------
>     Attachment: refConstraint2005-06-07.diff
> [PATCH] This patch supersedes my previous patch. It incorporates Dan's request that Derby
behave as it did in V10.0 on databases that have been soft upgraded from V10.0. That is, if
the database is a V10.0 database then Derby 10.1 will not allow the creation of referential
constraints with potentially conflicting actions. Derby 10.0 did not allow creation of such
constraints and is not prepared to handle the case where one referential constraint action
requires that a column be set to null while another referential constraint action requires
that the row be deleted.

Is the hash table you build at execution time for the affected rows
always built, or only if there is a potential for conflicting actions?


View raw message