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

Kim Haase commented on DERBY-6571:
----------------------------------

I'm working on making your suggested fixes, Dag.

For rrefsqlj13590.html, would the following wording be correct?

"When a deferrable constraint's constraint mode is DEFERRED before execution of 
a statement starts, the checking of the constraint does not take place at the 
end of the statement execution as usual, but only when it is explicitly or 
implicitly requested using one of the following mechanisms:"

As for the second one (the language appears both in the JTA topic and the SET 
CONSTRAINTS topic), I am a little perplexed. I saw the second paragraph in the 
spec under "XA Run-time Behavior." However, the second paragraph appears to 
refer to a two-argument form of the javax.transaction.xa.XAResource.prepare 
method, which doesn't seem to exist; the only documented form is with one 
argument, Xid. And the behavior seemed exactly the same for both forms anyway. 
I should have questioned this instead of just leaving it out. 

Thanks in advance for your advice!

> 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