[
https://issues.apache.org/jira/browse/DERBY-6571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007736#comment-14007736
]
Dag H. Wanvik commented on DERBY-6571:
--------------------------------------
Thanks Kim,
I updated the functional specification with a fix to the second XA paragraph:
it had en error, the method should be "commit", not "prepare" there. It also
has an extra argument, even in the present (albeit wrong) version.
I think it would be good to include the XA info both under the run-time
behavior of Deferrable constraints as well as next to the XA prepare mention,
and possibly XA commit(d call(Xid, true) method if *that* is ever mentioned
anywhere... We did mention the possibility of errors next to ordinary commit
too.
As for SQL states, you can omit those - it seems our practice is not to mention
them... although didn't we have a (generated) list somewhere?
I'll review the latest patch for the usage of "deferrable".
> 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)
