[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-4661) Properly propagate Query.setLockMode to Hibernate Core

Steve Ebersole (JIRA) noreply at atlassian.com
Tue Feb 2 14:12:29 EST 2010


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

Steve Ebersole commented on HHH-4661:
-------------------------------------

Part of the change here needs to be application of "force increment" locks from query lock modes.  Currently that does not happen.  In terms of impl, what I think needs to happen is that we do this per effective lock mode for each result.  The distinction is that in Hibernate queries, the lock modes are indicated per alias while JPA only defines a single lock mode for the query

> Properly propagate Query.setLockMode to Hibernate Core
> ------------------------------------------------------
>
>                 Key: HHH-4661
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4661
>             Project: Hibernate Core
>          Issue Type: Sub-task
>          Components: entity-manager
>            Reporter: Emmanuel Bernard
>            Assignee: Steve Ebersole
>             Fix For: 3.5.0-Next
>
>          Time Spent: 2 hours, 42 minutes
>  Remaining Estimate: 0 minutes
>


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