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

[Steve Ebersole (JIRA)]

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

Steve Ebersole edited comment on HHH-6736 at 5/1/12 7:42 AM:
-------------------------------------------------------------

See pull-request: https://github.com/hibernate/hibernate-orm/pull/323

      was (Author: aleksabl):
    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: https://hibernate.onjira.com/browse/HHH-6736
>             Project: Hibernate ORM
>          Issue Type: New Feature
>          Components: core
>            Reporter: Aleksander Blomskøld
>              Labels: dialect, 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