It would be desirable to configure envers in that way, that the audit tables only contain historic revisions, excluding the current revision. With this, the main table would contain the current revision and the audit table would contain all revisions before the current revision.

The main reason for this feature request is the fact, that we're using liquibase in our project to manage database migration. Since we're dealing with lot's of master data (with the requirement to audit all of them) wich is inserted into database via liquibase, we would be forced to insert the audit data beside the revision meta data by hand. The requested feature would free us from this, since the first historic revision would be inserted into the audit log before the first update event.

We tried to used conditional auditing, as described in developer guide. Since envers architecture seems to be build upon POST (post update for example) events instead of PRE (pre update for example) events, we weren't able to design a working concept as all the listeners assume post events.

It would be fine if you'd evaluate this feature request. We can imagine that it is interesting for projects which use a db migration tool like liquibase and envers to audit changed on entities