[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4130?page=c...
]
Ryan Reck updated HHH-4130:
---------------------------
Attachment: hibernate-HHH-4130.patch
I ran into the same problem, here's a patch to fix it (against 3.3.2.GA). I have no
test case I can submit, but the error I was getting has gone away.
The EntityManager.lock() uses the wrong column name when it is passed
a sub-type entity from a joined inheritance strategy
--------------------------------------------------------------------------------------------------------------------------
Key: HHH-4130
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4130
Project: Hibernate Core
Issue Type: Bug
Components: entity-manager
Environment: Hibernate 3.3.1 Annotations 3.4
Reporter: mike wray
Priority: Minor
Attachments: hibernate-HHH-4130.patch
I would expect to see:
update SUPER set ROW_VERSION_SEQ=? where SUPER_ID=? and ROW_VERSION_SEQ=?
but instead I see:
update SUPER set ROW_VERSION_SEQ=? where SUB_ID=? and ROW_VERSION_SEQ=?
which throws a org.hibernate.exception.SQLGrammarException: could not retrieve version.
This is because column SUB_ID does not exist on table SUPER.
--
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