[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5275) Criteria.setLockMode does not work correctly
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5275?page=c...
]
Steve Ebersole commented on HHH-5275:
-------------------------------------
The developer meeting is held on IRC, #hibernate-dev on freenode. You just have to be a
registered freenode user.
I understand what you want. But as a developer I am sure you also understand the
unworkability of maintaining bug fixes for all versions you have ever released. Thats
simply not scalable. We would do nothing else ever but backport fixes between our various
release branches.
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