[
http://opensource.atlassian.com/projects/hibernate/browse/EJB-387?page=co...
]
Jaroslaw Gilewski commented on EJB-387:
---------------------------------------
Hi,
I have noticed the same problem in my application.
Regards
Jarek
The EntityManager.lock() uses the wrong column name when it is passed
a sub-type entity from a joined inheritance strategy
--------------------------------------------------------------------------------------------------------------------------
Key: EJB-387
URL:
http://opensource.atlassian.com/projects/hibernate/browse/EJB-387
Project: Hibernate Entity Manager
Issue Type: Bug
Components: EntityManager
Affects Versions: 3.4.0.GA
Environment: Hibernate 3.3.1 Annotations 3.4
Reporter: mike wray
Priority: Minor
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