11 Replies Latest reply on Dec 1, 2010 7:40 PM by Sviatoslav Reentenko

    Audit records for entities that weren't actually modified

    Scott Mueller Newbie

      We've migrated our old revision history mechanism over to envers and I see now that there are tons of duplicate records in the audit tables.  For example, a top level entity in our object hierarchy is updated, but no fields have changed.  Envers not only records a record for it in its _AUD table, but also for every single one of the dependent entities as well...  it's a real duplication mess.

       

      Is envers supposed to record audit records even when no fields have been modified on an entity?  If so, how can we prevent this behavior?  Do I really have to look up in the db every single field of every single dependent entity and compare when updating an entity?