Return-Path: Delivered-To: apmail-openjpa-users-archive@locus.apache.org Received: (qmail 59874 invoked from network); 19 Dec 2008 03:30:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Dec 2008 03:30:58 -0000 Received: (qmail 6651 invoked by uid 500); 19 Dec 2008 03:31:10 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 6628 invoked by uid 500); 19 Dec 2008 03:31:10 -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 6617 invoked by uid 99); 19 Dec 2008 03:31:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Dec 2008 19:31:10 -0800 X-ASF-Spam-Status: No, hits=2.4 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of prashant.mr@gmail.com designates 209.85.142.184 as permitted sender) Received: from [209.85.142.184] (HELO ti-out-0910.google.com) (209.85.142.184) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Dec 2008 03:30:49 +0000 Received: by ti-out-0910.google.com with SMTP id w7so743720tib.13 for ; Thu, 18 Dec 2008 19:30:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=0EPezlTqxP/Mj4CJOxGdS23hULFrlNpTDiSyd6Fv2p0=; b=kmKGJ4D6VKRnGJk57GHi4NCmV07wrLAnGcEaVZedw85df43gGqzMIbnbgwYfrdyUio +XY4s9vEuyiBJ5M5AhwUMqoXb8GcsxdLDpnR6M8Sy5TM48OG39+in6JkTfmnzUEdiWfi zc/XfbtREkTLZdUp4w5uAwciCOsVzYwu1X1pI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=nt/5aXVwUKBAWo03MEKq824EWpvFxDVc/0FOY0+EG0y3CZ6ejEsar+Bdb26qLmudjY t7cz2ObD3T0KM0aq6xs1qaxJuAWVfaGPGbP9quGBku90YcWUWSa3+G/5VgATTBV5LR+C 59aRh5Lg/fENRe7Z7LLFwbv+Rfl947yhYETzY= Received: by 10.110.17.6 with SMTP id 6mr3891338tiq.59.1229657426349; Thu, 18 Dec 2008 19:30:26 -0800 (PST) Received: by 10.110.47.7 with HTTP; Thu, 18 Dec 2008 19:30:26 -0800 (PST) Message-ID: <3f5f9f310812181930t2d103ef8h35d1f043f85fe2e@mail.gmail.com> Date: Fri, 19 Dec 2008 11:30:26 +0800 From: "Prashant Bhat" To: users@openjpa.apache.org Subject: Re: Schema generation with unique constraints In-Reply-To: <1226601678022-1495039.post@n2.nabble.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_27404_32113429.1229657426345" References: <49143734.5000305@bitspot.com> <1226077588931-1470609.post@n2.nabble.com> <4917EC18.1050700@bitspot.com> <1226333330990-1481092.post@n2.nabble.com> <3f5f9f310811130234n7007a093i17205696b9c3d5@mail.gmail.com> <1226601678022-1495039.post@n2.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_27404_32113429.1229657426345 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, Could this change(rev# 713778) be applied to 1.3.x branch as well? Thanks, Prashant On Fri, Nov 14, 2008 at 2:41 AM, Pinaki Poddar wrote: > > Hi, > > Will you please try the latest check-in 713778? I have essentially > reverted to 1.1.0 scheme of naming the constraints. If possible use a > database that does *not* allow identically named constraints across > different tables (e.g. HSQLDB, I presume). Also see if the associated test > cases can be bolstered. > > The problem of generating unique naming could have had a simpler solution > if JPA spec allowed a constraintName attribute for @UniqueConstraint and > @Column(unique=true). > > Pinaki > -- > View this message in context: > http://n2.nabble.com/Schema-generation-with-unique-constraints-tp1469373p1495039.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. > > ------=_Part_27404_32113429.1229657426345--