[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5275) Criteria.setLockMode does not work correctly
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5275?page=c...
]
Graeme Rocher commented on HHH-5275:
------------------------------------
@Steve - I understand it is not easy, and if you don't feel it is a reasonable request
then there is nothing I can do. However, note that this is a regression of previous
behavior that worked in 3.3.x.
In addition upgrading to Hibernate 4 is non-trivial both for us and Grails users as it has
several breaking changes to the package structure. We are going to have to maintain 2
separate hibernate plugins, one for Hibernate 3 and another for Hibernate 4 so that
existing Grails applications have an upgrade path.
I am happy to submit a pull request to fix the issue in the 3.6.x branch and collaborate
on the fix if that helps. If not then I guess there is nothing I can do and Grails users
will have to live with this broken functionality.
Criteria.setLockMode does not work correctly
--------------------------------------------
Key: HHH-5275
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5275
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.2, 3.5.3
Environment: Hibernate 3.5.2, Oracle 10 (using
org.hibernate.dialect.Oracle10gDialect
Reporter: Björn Moritz
Assignee: Steve Ebersole
Priority: Minor
Fix For: 4.0.1
Attachments: AnotherOracle10gDialect.java, My_Oracle10Dialect.java,
My_Oracle10Dialect.java, TestCase.zip
Time Spent: 2h 19m
The LockMode set via Criteria.setLockMode does not generate a ' for update' SQL
statement. In the org.hibernate.dialect.Dialect class only the LockOptions are used for
determining a possible addition to the SQL statement if using pessimistic locking. This
behaviour is different from Hibernate 3.1.3.
In the supplied TestCase two threads are reading the same database record; one of those
threads should use pessimistic locking thereby blocking the other thread. But both threads
can read the database record causing the test to fail.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira