[
https://issues.apache.org/jira/browse/DERBY-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13736864#comment-13736864
]
Dag H. Wanvik edited comment on DERBY-532 at 8/12/13 1:40 PM:
--------------------------------------------------------------
Uploading derby-532-syntax-binding-dict-2, which builds on patch #1 (apply
consecutively).
Elaborates ALTER TABLE ALTER TABLE, correcting syntax, adding name binding and
updating dictionary (subject to the property derby.constraintsTesting) in a new
AlterConstraintConstantAction class.
Built out tests in ConstraintCharacteristicsTest to systematically check all
possible characteristics combinations in all cases, and adding tests for ALTER
TABLE ALTER TABLE, including dictionary updates.
Regressions ran ok.
was (Author: dagw):
Uploading derby-532-syntax-binding-dict-2, which builds on patch #1 (apply
consecutively).
Elaborates ALTER TABLE ALTER TABLE, correcting syntax, adding name
binding and updating dictionary (subject to the property
derby.constraintsTesting) in a new AlterConstraintConstantAction
class.
Built out tests in ConstraintCharacteristicsTest to systematically
check all possible characteristics combinations in all cases, and
adding tests for ALTER TABLE ALTER TABLE, including dictionary
updates.
Regressions ran ok.
> 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
