[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

[ https://hibernate.onjira.com/browse/HHH-7295?page=com.atlassian.jira.plug... ] Lukasz Antoniak commented on HHH-7295: -------------------------------------- Envers has a concept of audit entities which store historical data. If {{ValidityAuditStrategy}} is used, audit tables contain extra column {{END_REV}} which points to the last revision when particular data was valid. This allows generating more efficient queries. When an entity gets modified, we need to update {{END_REV}} of the last corresponding (matched by id) entry in the audit table. To achieve this {{ValidityAuditStrategy}} executes SELECT FOR UPDATE and then UPDATE. SELECT FOR UPDATE can cause issues for some dialects with inheritance mappings. I have been working on the workaround: https://github.com/lukasz-antoniak/hibernate-core/commit/5d2e6dc5ebcac5bb.... This works and waits for Adam to review. Upgrade lock has been added to resolve HHH-6647. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira