[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5183) Use the same @SecondaryTable on a class and its subclass

[Nicolas Romanetti (JIRA)]

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

Nicolas Romanetti commented on HHH-5183:
----------------------------------------

Hello Emmanuel,
As you can imagine I encounter this approach on a large legacy schema.
I admit it is not super right.
Nicolas


> Use the same @SecondaryTable on a class and its subclass
> --------------------------------------------------------
>
>                 Key: HHH-5183
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5183
>             Project: Hibernate Core
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 3.5.1
>         Environment: Hibernate 3.3.2.GA
> H2 Database version 1.2.131
>            Reporter: Nicolas Romanetti
>
> When @SecondaryTable is declared (with the same secondary table name) 
> in 2 distinct entities that belong to the same hierarchy (single table inheritance), hibernate considers 
> that the secondary tables are different! 
> Indeed, when persisting the entity, if the properties (using the secondary table) are set in
> the entity itself and its parent, hibernate does 2 inserts on the secondary table instead of one
> (one for the 'secondary' property of the parent, and one for the 'secondary' property of the current entity)
> This triggers a pk violation exception as the same PK is used twice on the secondary table.

-- 
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