[
https://issues.apache.org/jira/browse/DERBY-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749998#comment-13749998
]
Dag H. Wanvik edited comment on DERBY-532 at 8/26/13 11:12 AM:
---------------------------------------------------------------
Thanks, Rick. You need the -p1 option to patch for git generated diffs. I'll
add more comments about the encoding scheme.
As far as invalidation, I am not sure yet; it will depend on whether we
generate different code for enforced/not enforced. Most likely, it will be
"yes".
was (Author: dagw):
Thanks, Rick. You need the -p1 option to patch for git generated diffs.
I'll add more comments about the encoding scheme.
As far as invalidation, I am not sure yet; it might depend on whether we
generate different code for enforced/not enforced. Most likely, it will be
"yes".
> Support deferrable constraints
> ------------------------------
>
> Key: DERBY-532
> URL: https://issues.apache.org/jira/browse/DERBY-532
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Reporter: Jörg von Frantzius
> Assignee: Dag H. Wanvik
> Labels: derby_triage10_11
> Attachments: deferredConstraints.html, deferredConstraints.html,
> derby-532-syntax-binding-dict-1.diff, derby-532-syntax-binding-dict-1.status,
> derby-532-syntax-binding-dict-2.diff, derby-532-syntax-binding-dict-2.status
>
>
> In many situations it is desirable to have constraints checking taking place
> only at transaction commit time, and not before. If e.g. there is a chain of
> foreign key constraints between tables, insert statements have to be ordered
> to avoid constraint violations. If foreign key references are circular, the
> DML has to be split into insert statements and subsequent update statements
> by the user.
> In other words, with deferred constraints checking, life is much easier for
> the user. Also it can create problems with softwares such as
> object-relational mapping tools that are not prepared for statement ordering
> and thus depend on deferred constraints checking.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
