Message Title

The "initialize envers with legacy database" approach is perfect when you have existing database and you simply start using envers in the project. Thanks for sharing the code!

This doesn't help, however, for those using conditional auditing (as mentioned in comment above).

It turns out the solution is really simple. I've been using the following code for 2y now:

>From 9306c180c7a19d59ff68ebeb6cdc96939e783ed7 Mon Sep 17 00:00:00 2001
From: Piotr Findeisen <piotr.findeisen@syncron.com>
Date: Wed, 28 Aug 2013 16:49:42 +0200
Subject: [PATCH] [syncron] BPP-10539 / HHH-8456: support case when AUD data
 missing

---
 .../java/org/hibernate/envers/strategy/ValidityAuditStrategy.java    | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/hibernate-envers/src/main/java/org/hibernate/envers/strategy/ValidityAuditStrategy.java b/hibernate-envers/src/main/java/org/hibernate/envers/strategy/ValidityAuditStrategy.java
index ee554b2..2a52fa7 100644
--- a/hibernate-envers/src/main/java/org/hibernate/envers/strategy/ValidityAuditStrategy.java
+++ b/hibernate-envers/src/main/java/org/hibernate/envers/strategy/ValidityAuditStrategy.java
@@ -207,9 +207,8 @@ public class ValidityAuditStrategy implements AuditStrategy {
                        );
 
                        if ( rowCount != 1 ) {
-                               throw new RuntimeException(
-                                               "Cannot update previous revision for entity " + auditedEntityName + " and id " + id
-                               );
+                               // BPP-10539 / HHH-8456: support case when AUD data missing /PIOFIN 20130827
+                               // throw new RuntimeException("Cannot update previous revision for entity " + auditedEntityName + " and id " + id);
                        }
                }
     }
-- 
1.9.2