[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-7295) ParentAuditing Test in Envers Testsuite fails across different databases with different error messages because Hibernate does not set LockMode correctly

[Steve Ebersole (JIRA)]

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

Steve Ebersole commented on HHH-7295:
-------------------------------------

As I commented on JBPAPP-8892 I completely disagree that Hibernate should be using different lock modes here.  This is first and foremost a user API.  The user has requested an explicit lock type.  It is never good form to then try something else.

Instead, I think it is probably better to either:
1) apply lock modes differently in the case of joins and unions (which according to JBPAPP-8892 seems to really be the cause of the problem)
2) have Envers do something else here; but I do not fully understand what is trying to be achieved here, so I cannot say what that "something else" might be.  Adam and Lukasz, thoughts (added y'all as watchers)?

> ParentAuditing Test in Envers Testsuite fails across different databases with different error messages because Hibernate does not set LockMode correctly
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HHH-7295
>                 URL: https://hibernate.onjira.com/browse/HHH-7295
>             Project: Hibernate ORM
>          Issue Type: Bug
>          Components: envers
>    Affects Versions: 4.1.2
>            Reporter: Madhumita Sadhukhan
>            Assignee: Strong Liu
>
> Please refer https://issues.jboss.org/browse/JBPAPP-8892 for details

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