Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0EA1D101C6 for ; Wed, 20 Nov 2013 21:34:37 +0000 (UTC) Received: (qmail 25950 invoked by uid 500); 20 Nov 2013 21:34:36 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 25929 invoked by uid 500); 20 Nov 2013 21:34:36 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 25889 invoked by uid 99); 20 Nov 2013 21:34:36 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Nov 2013 21:34:36 +0000 Date: Wed, 20 Nov 2013 21:34:36 +0000 (UTC) From: "Dag H. Wanvik (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DERBY-532) Support deferrable constraints MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-532?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-532: -------------------------------- Attachment: (was: derby-532-post-scan-3.diff) > Support deferrable constraints > ------------------------------ > > Key: DERBY-532 > URL: https://issues.apache.org/jira/browse/DERBY-532 > Project: Derby > Issue Type: Improvement > Components: SQL > Reporter: J=C3=B6rg von Frantzius > Assignee: Dag H. Wanvik > Labels: derby_triage10_11 > Attachments: IndexDescriptor.html, IndexDescriptorImpl.html, Inde= xRowGenerator.html, SortObserver.html, deferredConstraints.html, deferredCo= nstraints.html, deferredConstraints.html, deferredConstraints.html, derby-5= 32-import-1.diff, derby-532-import-1.status, derby-532-import-2.diff, derby= -532-import-3.diff, derby-532-import-3.status, derby-532-more-tests-1.diff,= derby-532-more-tests-1.stat, derby-532-post-scan-1.diff, derby-532-post-sc= an-1.stat, derby-532-post-scan-2.diff, derby-532-post-scan-2.stat, derby-53= 2-post-scan-3.diff, derby-532-post-scan-3.stat, derby-532-serializable-scan= -1.diff, derby-532-serializable-scan-2.diff, derby-532-serializable-scan-2.= stat, 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-dic= t-2.status, derby-532-syntax-binding-dict-all-1.diff, derby-532-testAlterCo= nstraintInvalidation.diff, derby-532-testAlterConstraintInvalidation.status= , derby-532-unique-pk-1.diff, derby-532-unique-pk-1.status, derby-532-uniqu= e-pk-2.diff, derby-532-unique-pk-3.diff, derby-532-unique-pk-3.status, derb= y-532-xa-1.diff, derby-532-xa-2.diff, derby-532-xa-3.diff, derby-532-xa-3.s= tatus > > > In many situations it is desirable to have constraints checking taking pl= ace only at transaction commit time, and not before. If e.g. there is a cha= in of foreign key constraints between tables, insert statements have to be = ordered to avoid constraint violations. If foreign key references are circu= lar, the DML has to be split into insert statements and subsequent update s= tatements by the user. > In other words, with deferred constraints checking, life is much easier f= or the user. Also it can create problems with softwares such as object-rela= tional mapping tools that are not prepared for statement ordering and thus = depend on deferred constraints checking. -- This message was sent by Atlassian JIRA (v6.1#6144)