Same for HQL/JPQL update/delete executions. But honestly, that is outside the scope of Envers. And really it is outside the scope of any solution outside the database. So I've converted this to a feature request, but I seriously doubt we will work on this any time soon. Really such a solution would need to be integrate at the database level (triggers, etc).