[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-6736) Support for SELECT ... FOR UPDATE SKIP LOCKED / read past locking

Aleksander Blomskøld (JIRA) noreply at atlassian.com
Wed Oct 19 05:32:21 EDT 2011


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

Aleksander Blomskøld commented on HHH-6736:
-------------------------------------------

See pull-request: https://github.com/hibernate/hibernate-core/pull/192

> Support for SELECT ... FOR UPDATE SKIP LOCKED / read past locking
> -----------------------------------------------------------------
>
>                 Key: HHH-6736
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6736
>             Project: Hibernate Core
>          Issue Type: New Feature
>          Components: core
>            Reporter: Aleksander Blomskøld
>              Labels: dialect, hibernate, locks
>
> Hibernate does currently not support SKIP-LOCKED locking. Skip locked-semantics is useful in when having queue tables with several concurrent consumers. It is supported by Oracle (after 10g, documented in 11g), SQL Server (with the readpast hint), Sybase and possibly others.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the hibernate-issues mailing list