db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6576) A immediate Fk constraint blows up iff its referenced PK is deferred and we modify a duplicate key column
Date Mon, 02 Jun 2014 22:37:02 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14015985#comment-14015985
] 

ASF subversion and git services commented on DERBY-6576:
--------------------------------------------------------

Commit 1599383 from [~dagw] in branch 'code/trunk'
[ https://svn.apache.org/r1599383 ]

DERBY-6576 A immediate Fk constraint blows up iff its referenced PK is deferred and we modify
a duplicate key column

Patch derby-6576-forbid-deferred+cascade-set-null-1. It simplifies the
code of the previous patch for thi sissue that handles RESTRICT and NO
ACTION in combination with a deferrable primary key. It also forbids
CASCADE and SET NULL of the target primary key is deferrable, at least
for now until a satisfactory implementation can be found. Test have
been added for the new cases.

> A immediate Fk constraint blows up iff its referenced PK is deferred and we modify a
duplicate key column
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6576
>                 URL: https://issues.apache.org/jira/browse/DERBY-6576
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>         Attachments: derby-6576-2.diff, derby-6576-3.diff, derby-6576-3.status, derby-6576-cascade-setnull.diff,
derby-6576-cascade-setnull.status, derby-6576-forbid-deferred+cascade-set-null-1.diff, derby-6576-forbid-deferred+cascade-set-null-1.status,
derby-6576.diff, derby-6576.status
>
>
> Similar to the issue in DERBY-6559, except here we modify the key in the referenced table.
This leads Derby to check for any referencing FK and throw, even if there are other (formerly)
duplicate rows that satisfy the FK constraint.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message