[
https://issues.apache.org/jira/browse/DERBY-6571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018750#comment-14018750
]
Dag H. Wanvik commented on DERBY-6571:
--------------------------------------
As for the final sentence: "Derby performs constraint checks at the time the
statement is executed, unless the constraint's mode is DEFERRED, see above."
you changed that in a way that's not entirely accurate by mentioning only
commit as a possible constraint checking time:
"If the constraint mode is not DEFERRED, Derby performs constraint checks at
the time the statement is executed, not when the transaction commits. See..."
I think I'd like to change this to
"If the constraint mode is IMMEDIATE (the default), Derby performs constraint
checks at the time the statement is executed. If the constraint mode is
DEFERRED, the checking is done later, typically at commit time. See.."
The key difference here is the word "typically": the checking could also happen
if we explicitly set the constraint mode to IMMEDIATE explicitly or return from
a routine, but we say that elsewhere, so I think we can just say "typically"
here..?
> 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-6.diff, DERBY-6571-6.stat, DERBY-6571-6.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)
