[
https://issues.apache.org/jira/browse/DERBY-6571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008936#comment-14008936
]
Dag H. Wanvik commented on DERBY-6571:
--------------------------------------
Thanks, Kim. Here are the remaining comment :)
- devguide/cdevconcepts838850: OK
- ref/crefsqlj35312: OK
- ref/rrefcreatefunctionstatement: OK
- ref/rrefcreateprocedurestatement: OK
- rrefjta1003415:
The section title is somewhat at odds with what we are now putting
in there, but apparently there isn't any other place where we
discuss behavior for the XA API methods. Perhaps we'd better make
another section, e.g. "XA transactions and deferred constraints".
- ref/rrefsqlj13590:
Paragraph starting with "If a foreign key is deferrable, ..."
The sentence isn't precise enough, I suggest:
"If a foreign key's constraint mode is deferred, ..."
"ON DELETE or ON UPDATE action specification" -> "ON DELETE or ON
UPDATE referential action specification"
"Only if NO ACTION has been specified is the checking deferred." ->
"Only if NO ACTION has been specified is the checking ever deferred."
"If the primary table's referenced primary or unique key constraint is also
deferrable," ->
"If the primary table's referenced primary or unique key constraint is also
deferred,"
", if the foreign key is also deferrable," ->
", if the foreign key is also deferred,"
- ref/rrefsqlj16095: OK
- ref/rrefsqlj42154: OK
- ref/rrefsqljconstrchar:
It may be good to add a caveat in this section on performance:
"Deferred constraints sometimes impose extra performance overhead to
allow for the deferred checking. If your application does not
require deferred checking, we recommend declaring constraints as NOT
DEFERRABLE (the default)."
- ref/rrefsqljsetconstr:
"When you change the constraint mode explicitly using SET
CONSTRAINTS, the constraint is checked, but slightly differently
from the way it is checked at commit time: if a violation is found,
a statement-level exception is thrown."
->
"When you change the constraint mode explicitly to IMMEDIATE using
SET CONSTRAINTS, the constraint is checked, but slightly
differently from the way it is checked at commit time: if a
violation is found, a statement-level exception is thrown."
> 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-4.diff,
> DERBY-6571-4.stat, DERBY-6571-4.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)
