[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5947) @UniqueConstraint does not take into account properties from @MappedSuperClass when those are @ManyToOne

[Manuel Bernhardt (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40050#action_40050 ] 

Manuel Bernhardt commented on HHH-5947:
---------------------------------------

Ok, of course I figured out this is not a bug right after submitting a test case for it.

The problem is that the @UniqueConstraint annotation really does expect database-level column names, whereas it seems very intuitive that those names should be entity-level names (and, yes, the doc says otherwise, but it's not very clear there either).

The pull request now features a "fix" that improves the error message. Additionally the test case test the @UniqueConstraint (so far I haven't found a test doing that in the hibernate-core test suite).

> @UniqueConstraint does not take into account properties from @MappedSuperClass when those are @ManyToOne
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HHH-5947
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5947
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: annotations
>    Affects Versions: 3.6.1
>            Reporter: Manuel Bernhardt
>
> Given a @MappedSuperclass with a @ManyToOne relation, this relation cannot be used in a subclass @UniqueConstraint (it is not found).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira