CODEWITHSUNDEEP
databasedatabase-designjakarta-eejpa
Buddhika Ariyaratne
Buddhika Ariyaratne

Reputation: 2431

What is the best way to record the edit history in a database

I am developing a system with Java EE and JPA where users can make changes to entities. It is needed to trace back to the changes when needed. So the all the changes and the user have to be recorded for each occasion when en update is made. What is the best way to record the changes.

For example, there is an Entity called Investigation. It has attributes like Name, Category, Price, Volume, etc. A user can search a single investigation and change the name in one instance and in another instance, another user can change the price. All these occasions with the change done and the user who did it is needed to be traced back when needed.

One method described in this link is that to label objects as old edited and create a new object with updated values, but the problem there are several other objects from different entities referring to the old one.

Another method as described in this link is to use a versioning field in a new table. Than can be achieved in JPA by creating a new entity that extends the main entity.

Out of these methods what is the best practice? Is there any other optimized way to keep the record editing history in Java Persistence?

Upvotes: 1

Views: 1800

Answers (2)

James
James

Reputation: 18389

EclipseLink supports history.

See, http://wiki.eclipse.org/EclipseLink/Examples/JPA/History

Upvotes: 2

Tomasz Nurkiewicz
Tomasz Nurkiewicz

Reputation: 340963

If you don't mind using Hibernate, Envers might be interesting for you. It performs auditing automatically, optionally appending metadata like current user.

For each audited entity it creates a history table that holds previous versions.

Upvotes: 2

Related Questions