[
https://issues.apache.org/jira/browse/OPENJPA-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776903#action_12776903
]
Pinaki Poddar commented on OPENJPA-1047:
----------------------------------------
These commits 835292 & 293 are wrongly assigned to this issue. They actually
pertains to OPENJPA-1046.
> 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: 1.2.1
> Reporter: Pinaki Poddar
> Assignee: Pinaki Poddar
> Fix For: 2.0.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.
-
You can reply to this email to add a comment to the issue online.
