[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-1518) Guarentee LockMode behaviors

[Steve Ebersole (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Ebersole closed HHH-1518.
-------------------------------


Closing stale resolved issues

> Guarentee LockMode behaviors
> ----------------------------
>
>                 Key: HHH-1518
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1518
>             Project: Hibernate Core
>          Issue Type: Improvement
>          Components: core
>            Reporter: Steve Ebersole
>            Assignee: Steve Ebersole
>             Fix For: 3.2.0.alpha1
>
>
> The current thought process behind applying lock modes is to simply assume that the given database supports such locking-level/isolation.  In the case where a database does not, the effect is that we "gracefully" fall back to a lower LockMode.  
> Consider HSQLDB as an example.  It does not support any isolation level other than READ_UNCOMMITTED.  If a user attempts a session.lock( myEntity, LockMode.UPGRADE ) the net effect on HSQLDB is that essentially nothing happens; no form of write lock is acquired in the database.
> The other concern is databases which do not support write lock acqusition through selects (i.e., no "SELECT ... FOR UPDATE" syntax or variation).  The only way to acquire write locks on these databases is to perform a write.

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