[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5183?page=c...
]
Gail Badner commented on HHH-5183:
----------------------------------
Is this still an issue with 3.5.1?
If so, please check to see if it is already an unresolved issue reported for 3.5.x:
http://opensource.atlassian.com/projects/hibernate/secure/IssueNavigator....
To see if it has been fixed for the next 3.5.x release:
http://opensource.atlassian.com/projects/hibernate/secure/IssueNavigator....
If this is still an issue in 3.5.1, then please attach a unit test that reproduces your
issue. You may find an existing unit test in testsuite.
Thanks,
Gail
Inheritance (single table) and @SecondaryTable
-----------------------------------------------
Key: HHH-5183
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5183
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.3.2
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira