[
https://issues.apache.org/jira/browse/DERBY-6571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007355#comment-14007355
]
Dag H. Wanvik commented on DERBY-6571:
--------------------------------------
I believe the right term is "deferrable constraints". The short hand "deferred
constraints" really means a "deferrable constraint" that has constraint mode
"deferred". C.f. this quote from the standard:
{quote}
"Every constraint is either deferrable or non-deferrable. Within an
SQL-transaction, every constraint has a
constraint mode; if a constraint is non-deferrable, then its constraint mode is
always immediate; otherwise, it
is either immediate or deferred."
{quote}
Sorry that lack of precision sneaked into the functional specification ;-)
> 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
> 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.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)
