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

Dag H. Wanvik commented on DERBY-6571:
--------------------------------------

Hi Kim, I have added a limitation to the implementation which we should 
document, cf. version 1.9 of the functional specification.
It should go under foreign keys (section rrefsqlj13590.html, subsection 
"Foreign key constraints"), just before the final "Note" paragraph, perhaps - 
no, make it the third but the last paragraph: "If the references clause 
contains a CASCADE or SET NULL referential action, the primary or unique key 
referenced must not be deferrable".

Now that I look at this section again, I also see the following statement which 
is no longer accurate:

(subsection "Foreign key constraints and DML"):

"Derby performs constraint checks at the time the statement is executed, not 
when the transaction commits."

This should be, now that a foreign key constraint can deferred,

"Derby performs constraint checks at the time the statement is executed, unless 
the constraint's mode is DEFERRED, see above." ?

> Document deferrable constraints
> -------------------------------
>
>                 Key: DERBY-6571
>                 URL: https://issues.apache.org/jira/browse/DERBY-6571
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Documentation
>            Reporter: Dag H. Wanvik
>            Assignee: Kim Haase
>              Labels: derby_backport_reject_10_10
>             Fix For: 10.11.0.0
>
>         Attachments: DERBY-6571-2.diff, DERBY-6571-2.stat, DERBY-6571-2.zip, 
> DERBY-6571-3.diff, DERBY-6571-3.stat, DERBY-6571-3.zip, DERBY-6571-4.diff, 
> DERBY-6571-4.stat, DERBY-6571-4.zip, DERBY-6571-5.diff, DERBY-6571-5.stat, 
> DERBY-6571-5.zip, DERBY-6571.diff, DERBY-6571.stat, DERBY-6571.zip
>
>
> The contents of functional specification attached to DERBY-532 should be 
> included in the documentation.



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

Reply via email to