How to store only the last revision

chris.simons Dec 9, 2009 9:40 PM

In an effort to conserve space in our database, I was wondering if there is an 'easy' way to only store the last revision with Envers? There might be some tables where I want the full revision history while others in which I only care about the latest revision.

Not using Envers for the latter tables then means I have to track and store that timestamp and user information manually, which defeats the purpose of Envers.

Has anyone implemented anything similar?

Thanks.

1. Re: How to store only the last revision

adamw Dec 12, 2009 6:24 AM (in response to chris.simons)

Hello,

out-of-the-box it isn't possible, but it should be doable with not too much effort. If you really want to only store the last revision (which is equal to the current state of the DB), why not audit just the ID?

Adam
Actions
2. Re: How to store only the last revision

chris.simons Dec 13, 2009 11:29 AM (in response to adamw)

Adam - I never thought of that, would that also keep track of the timestamp information?

If so, great idea...I'll give it a try.
Actions
3. Re: How to store only the last revision

adamw Dec 14, 2009 10:17 AM (in response to chris.simons)

Actually, this may not work, as Envers will think that there are no changes in the entity - the only field audited being the id, which never changes. So you would have to override the changes-checks in the WorkUnits. Should be pretty straightforward .

Adam
Actions

Go to original post