openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-1047) Unique Constraint on sibling classes causes name conflict
Date Wed, 21 Sep 2011 15:53:09 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109596#comment-13109596
] 

Michael Dick commented on OPENJPA-1047:
---------------------------------------

FWIW I've updated the log entries for rev 835292 and 835293 to reflect the correct JIRA. I
can't unlink the commits though, or relink them to the correct issue. 

> Unique Constraint on sibling classes causes name conflict
> ---------------------------------------------------------
>
>                 Key: OPENJPA-1047
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1047
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jpa
>    Affects Versions: 2.2.0
>            Reporter: Pinaki Poddar
>            Assignee: Pinaki Poddar
>             Fix For: 2.2.0
>
>
> OpenJPA is not generating unique names for unique constraints properly. Shows up when
unique constrain is defined in sibling classes [1]
> [1] http://n2.nabble.com/UniqueConstraint-in-a-MappedSuperclass-not-working-tc2633410.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message