[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5275) Criteria.setLockMode does not work correctly

[Jakob Braeuchi (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39074#action_39074 ] 

Jakob Braeuchi commented on HHH-5275:
-------------------------------------

we are using 3.5.6.

setLockMode() also does not work for HQL-Queries, setLockOptions() worked for me:

// query1.setLockMode("cat", LockMode.UPGRADE);
query1.setLockOptions(new LockOptions(LockMode.UPGRADE));

i found a workaround using my own OracleDialect where i override the new method getForUpdateString(String aliases, LockOptions lockOptions):

    @Override
    public String getForUpdateString(String aliases, LockOptions lockOptions)
    {
        // BRJ: 10.11.2010: Workaround für Problem mit setLockMode() in Hibernate 3.5.6
        return getForUpdateString(aliases);
    }

this works for both criteria- and hql-queries.

> 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.1
>
>         Attachments: 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