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.
Thanks for the PR, , I'll have a look.
, I tried the test case using 5.1, but there was no test failure. Does this bug really affect 5.1?
@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.