Return-Path: Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: (qmail 54801 invoked from network); 6 May 2010 14:36:12 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 May 2010 14:36:12 -0000 Received: (qmail 14749 invoked by uid 500); 6 May 2010 14:36:12 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 14715 invoked by uid 500); 6 May 2010 14:36:12 -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 14707 invoked by uid 99); 6 May 2010 14:36:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 May 2010 14:36:12 +0000 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=AWL,SPF_HELO_PASS,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 May 2010 14:36:07 +0000 Received: from jim.nabble.com ([192.168.236.80]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1OA2Az-0001L8-CG for users@openjpa.apache.org; Thu, 06 May 2010 07:35:45 -0700 Date: Thu, 6 May 2010 07:35:45 -0700 (PDT) From: Pinaki Poddar To: users@openjpa.apache.org Message-ID: <1273156545372-5014509.post@n2.nabble.com> In-Reply-To: <1273132204931-5013016.post@n2.nabble.com> References: <1272961203123-5002254.post@n2.nabble.com> <1273101673571-5011595.post@n2.nabble.com> <1273132204931-5013016.post@n2.nabble.com> Subject: Re: ManyToMany relations violating unique constraints MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, Can you post the error? If business logic ensured that {P_TYPE_ID, P_VALUE_STRING} of Parameter are unique combination then what exactly was the state of the Parameter instance P that violated the unique constrain? One possibility is during merge() operation, OpenJPA has wrongly judged the persistent life-cycle state of a detached Parameter instance P, and tried to re-insert P. But more data points are needed to diagnose what is going wrong. ----- Pinaki -- View this message in context: http://openjpa.208410.n2.nabble.com/ManyToMany-relations-violating-unique-constraints-tp5002254p5014509.html Sent from the OpenJPA Users mailing list archive at Nabble.com.