[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-5275) Criteria.setLockMode does not work correctly
Gail Badner (JIRA)
noreply at atlassian.com
Wed May 4 02:02:07 EDT 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gail Badner updated HHH-5275:
-----------------------------
Fix Version/s: (was: 3.6.4)
(was: 4.0.0.Alpha3)
4.0.0.Beta1
3.6.5
> 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
> Priority: Minor
> Fix For: 3.6.5, 4.0.0.Beta1
>
> Attachments: AnotherOracle10gDialect.java, My_Oracle10Dialect.java, My_Oracle10Dialect.java, TestCase.zip
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list