[
https://issues.apache.org/jira/browse/DERBY-6571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003390#comment-14003390
]
Kim Haase commented on DERBY-6571:
----------------------------------
Thanks so much, Dag! I'm working on incorporating these.
There seems to be an unfinished sentence in this comment:
E.g. "If the check fails, the transaction is not rolled back; an
error here constitutes a statement level error only, so one can use
this statement to check if all constraints are fulfilled before
Before what? I hesitate to guess.
The information to be added about stored procedures -- I gather this is
specific to procedures and does not apply to functions? Or does it apply to
both?
I'm thinking the info probably belongs in the CONSTRAINT clause topic, but
there should be links to it from the topics on CREATE PROCEDURE (and maybe on
CREATE FUNCTION if applicable), as you say at the end.
In the suggested rewording below, should "referred" be "deferred"?
"any delete of a parent row can lead to a foreign key violation
immediately (or at deferred checking time, if the foreign key is also
referred, as the case may be) when the last of possibly several
key duplicates of the referenced key is deleted or updated"
I don't think we do discuss commits in the Reference Manual, but we do in the
Developer's Guide -- there's a whole section (multiple topics) on transactions.
There's a topic "Statement versus transaction runtime rollback" that might
benefit from a mention of constraints. Possibly others too. Is the behavior
different with auto-commit on vs. off? Let me know where you think the best
place to mention constraints might be.
Thanks again.
> 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.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)
