From open-jpa-dev-return-699-apmail-incubator-open-jpa-dev-archive=incubator.apache.org@incubator.apache.org Tue Sep 12 18:12:47 2006 Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 47850 invoked from network); 12 Sep 2006 18:12:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Sep 2006 18:12:46 -0000 Received: (qmail 54683 invoked by uid 500); 12 Sep 2006 18:12:46 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 54652 invoked by uid 500); 12 Sep 2006 18:12:46 -0000 Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: open-jpa-dev@incubator.apache.org Delivered-To: mailing list open-jpa-dev@incubator.apache.org Received: (qmail 54642 invoked by uid 99); 12 Sep 2006 18:12:46 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Sep 2006 11:12:46 -0700 Authentication-Results: idunn.apache.osuosl.org smtp.mail=awhite@bea.com; spf=pass X-ASF-Spam-Status: No, hits=1.8 required=5.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST Received-SPF: pass (idunn.apache.osuosl.org: domain bea.com designates 63.96.162.5 as permitted sender) Received: from ([63.96.162.5:54398] helo=ussjmh01.bea.com) by idunn.apache.osuosl.org (ecelerity 2.1 r(10620)) with ESMTP id 2E/30-04030-7A8F6054 for ; Tue, 12 Sep 2006 11:12:56 -0700 Received: from [172.17.31.239] (sj-iz-172-17-31-239.bea.com [172.17.31.239]) by ussjmh01.bea.com (Switch-3.2.2/Switch-3.2.2) with ESMTP id k8CICaMO006832 for ; Tue, 12 Sep 2006 11:12:36 -0700 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <635DB2CA-D031-4C3C-A95C-24507AC458F3@SUN.com> References: <14156901.1158019042738.JavaMail.jira@brutus> <3DB84D99-8C19-4168-A8D1-5FC1ED565073@SUN.com> <8B82BA34-FBFF-467A-980B-88DE8B563521@bea.com> <635DB2CA-D031-4C3C-A95C-24507AC458F3@SUN.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Abe White Subject: Re: [jira] Resolved: (OPENJPA-39) Cascade delete does not work with foreign key constraints Date: Tue, 12 Sep 2006 11:12:37 -0700 To: open-jpa-dev@incubator.apache.org X-Mailer: Apple Mail (2.752.2) X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0, Antispam-Data: 2006.8.29.135443 X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > I think that cascade delete is most commonly used where there is a > one-to-possibly-zero relationship (with a [zero or one or many]-to- > one on the other side). Thus, the other side has the foreign key, > and the side with the cascade delete definition is the side with > the existence that doesn't depend on the other side. So deleting > the other side first usually solves the timing issues. Does anyone else have an opinion on this? Should we consider the children to be deleted before parent when cascading a delete? I have no problem with that strategy. > >>>> Register now for BEA World 2006 --- See http://www.bea.com/ >>>> beaworld<< > > Thanks for the personal invitation. Yeah, I just noticed that they've added that to the outgoing signature. How obnoxious. Supposedly they're working on removing the signature for us. >>Register now for BEA World 2006 --- See http://www.bea.com/beaworld<< _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.