[hibernate-issues] [Hibernate-JIRA] Created: (HHH-2010) getForUpdateString is not correct in DB2Dialect; session.lock doesn't work as expected.

Lari Hotari (JIRA) noreply at atlassian.com
Thu Aug 17 03:45:19 EDT 2006


getForUpdateString is not correct in DB2Dialect; session.lock doesn't work as expected.
---------------------------------------------------------------------------------------

         Key: HHH-2010
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2010
     Project: Hibernate3
        Type: Bug

  Components: core  
    Versions: 3.1.3, 3.2.0.cr3    
 Environment: 3.1.3, DB2
    Reporter: Lari Hotari


The correct getForUpdateString for DB2 should be "for update with rr"

see:
http://opensource.atlassian.com/projects/hibernate/browse/HB-1032

DB2 will release all locks created in a result set if the isolation level is lower than TRANSACTION_SERIALIZABLE (RR in DB2). 

Locks and concurrency control in DB2:
http://publib.boulder.ibm.com/infocenter/db2help/topic/com.ibm.db2.udb.doc/admin/c0005266.htm
"
The duration of row locking varies with the isolation level being used:
    * UR scans: No row locks are held unless row data is changing.
    * CS scans: Row locks are only held while the cursor is positioned on the row.
    * RS scans: Only qualifying row locks are held for the duration of the transaction.
    * RR scans: All row locks are held for the duration of the transaction.
" 


-- 
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