Fixed
Details
Assignee
AdamAAdamAReporter
Michał SkowronekMichał SkowronekOriginal estimate
Time tracking
No time logged56h remainingComponents
Fix versions
Priority
Major
Details
Details
Assignee
AdamA
AdamAReporter
Michał Skowronek
Michał SkowronekOriginal estimate
Time tracking
No time logged56h remaining
Components
Fix versions
Priority
Created August 25, 2011 at 12:25 AM
Updated February 9, 2012 at 6:21 AM
Resolved January 20, 2012 at 11:51 PM
Users would be able to construct more meaningful audit queries if Envers had an option to store and query information about modifications of individual properties, e.g.:
getAuditReader().createQuery().forRevisionsOfEntity(clazz, false, false)
.add(AuditEntity.id().eq(id)).add(AuditEntity.property(propertyName).hasChanged());
With such a query, user will get only those revisions of (clazz, id), that modified property with propertyName.
Currently, to achieve that, user have to retrieve and compare manually two revisions, which increases complexity and decreases performance.