Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Multiple revisions are created during a single transaction with FlushMode COMMIT

Description

When the FlushMode is set to commit, a manual flush during a transaction leads to multiple audit revision to be created.

Consider the following example:

In the example the persisted entity should have the same revision number ass the revision number obtained before the flush. However, the entity will be assigned to a new revision number.

It seems that the AuditProcess does check for FlushMode COMMIT instead of FlushMode MANUAL. This has been introduced with 5.2.

caused by

Activity

Show:

Felix FeisstApril 4, 2017 at 6:23 AM

@Gail Badner, I think the bug has been introduced with 5.2. Therefore I set "worked in" version to 5.1.5 when I created this issue.

Former userApril 4, 2017 at 5:58 AM

, I tried the test case using 5.1, but there was no test failure. Does this bug really affect 5.1?

Chris CranfordMarch 21, 2017 at 1:10 PM

Thanks for the PR, , I'll have a look.

Felix FeisstMarch 16, 2017 at 8:51 PM

I have added a PR with a unit test and a fix: https://github.com/hibernate/hibernate-orm/pull/1851

Fixed

Details

Assignee

Reporter

Worked in

Components

Fix versions

Affects versions

Priority

Created March 16, 2017 at 8:45 PM
Updated April 14, 2017 at 10:13 AM
Resolved March 21, 2017 at 1:29 PM