openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prashant Bhat" <prashant...@gmail.com>
Subject Re: Schema generation with unique constraints
Date Fri, 19 Dec 2008 03:30:26 GMT
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 <ppoddar@apache.org> 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.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message