From derby-user-return-6984-apmail-db-derby-user-archive=db.apache.org@db.apache.org Thu Jun 14 08:18:49 2007 Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 82093 invoked from network); 14 Jun 2007 08:18:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Jun 2007 08:18:49 -0000 Received: (qmail 16318 invoked by uid 500); 14 Jun 2007 08:18:50 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 16290 invoked by uid 500); 14 Jun 2007 08:18:50 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 16279 invoked by uid 99); 14 Jun 2007 08:18:50 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jun 2007 01:18:50 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [192.94.38.131] (HELO relay1.mentorg.com) (192.94.38.131) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jun 2007 01:18:45 -0700 Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1HykXA-0003UT-JM from nick_williamson@mentor.com for derby-user@db.apache.org; Thu, 14 Jun 2007 01:18:24 -0700 Received: from svr-gbn-exc-02.mgc.mentorg.com ([137.202.9.214]) by SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 14 Jun 2007 01:18:24 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C7AE5C.92F52FC1" Subject: Deferrable constraints Date: Thu, 14 Jun 2007 09:18:22 +0100 Message-ID: <1A590FCC158A244B80DC7D09134B9AED02300239@svr-gbn-exc-02.mgc.mentorg.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Deferrable constraints Thread-Index: AceuXJKJnM3zkfZGRF2Uddzz7QxIRw== From: "Williamson, Nick" To: X-OriginalArrivalTime: 14 Jun 2007 08:18:24.0031 (UTC) FILETIME=[93A002F0:01C7AE5C] X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C7AE5C.92F52FC1 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, =20 I'm migrating an Oracle schema to the Derby environment. In Oracle, all my FK constraints are defined as INITIALLY DEFERRED DEFERRABLE, which means that the validation checking isn't performed until commit time. If I have parent table "A" and child table "B", I can create a row in table B first, then create a row in table A (in the same transaction) and the commit will be successful. Derby doesn't support INITIALLY DEFERRED DEFERRABLE and the validation seems to be performed immediately by default. Is there a way to over-ride this behaviour and emulate what I had in my Oracle environment? =20 TIA Nick ------_=_NextPart_001_01C7AE5C.92F52FC1 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi=20 all,
 
I'm = migrating an=20 Oracle schema to the Derby environment. In Oracle, all my FK constraints = are=20 defined as INITIALLY DEFERRED DEFERRABLE, which means that the = validation=20 checking isn't performed until commit time. If I have parent table "A" = and child=20 table "B", I can create a row in table B first, then create a row in = table A (in=20 the same transaction) and the commit will be successful. Derby doesn't = support=20 INITIALLY DEFERRED DEFERRABLE and the validation seems to be performed=20 immediately by default. Is there a way to over-ride this behaviour and = emulate=20 what I had in my Oracle environment?
 
TIA
Nick
------_=_NextPart_001_01C7AE5C.92F52FC1--