Return-Path: X-Original-To: apmail-openjpa-users-archive@minotaur.apache.org Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E8AC893EE for ; Thu, 13 Oct 2011 13:16:58 +0000 (UTC) Received: (qmail 40053 invoked by uid 500); 13 Oct 2011 13:16:58 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 40011 invoked by uid 500); 13 Oct 2011 13:16:58 -0000 Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@openjpa.apache.org Delivered-To: mailing list users@openjpa.apache.org Received: (qmail 40003 invoked by uid 99); 13 Oct 2011 13:16:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Oct 2011 13:16:58 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Oct 2011 13:16:52 +0000 Received: from jim.nabble.com ([192.168.236.80]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1REL9D-0003gJ-J0 for users@openjpa.apache.org; Thu, 13 Oct 2011 06:16:31 -0700 Date: Thu, 13 Oct 2011 06:16:31 -0700 (PDT) From: Pinaki Poddar To: users@openjpa.apache.org Message-ID: <1318511791576-6888860.post@n2.nabble.com> In-Reply-To: <1318373206825-6882907.post@n2.nabble.com> References: <1318373206825-6882907.post@n2.nabble.com> Subject: Re: Delete OptimisticLock exception, when entity appears 2x in cascade graph MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, > I'm not at liberty to change this structure or the RI. did you tell OpenJPA to read the database foreign key constraints? OpenJPA update can topologically sort a to-be-committed graph of objects to honor database constraints -- but the quality of sort depends on supplied information. If you have not, please see openjpa.jdbc.SynchronizeMappings property. ----- Pinaki Poddar Chair, Apache OpenJPA Project -- View this message in context: http://openjpa.208410.n2.nabble.com/Delete-OptimisticLock-exception-when-entity-appears-2x-in-cascade-graph-tp6882907p6888860.html Sent from the OpenJPA Users mailing list archive at Nabble.com.