Add possibility to integrate versioning infrastructure like Hibernate Envers [DATAJPA-7] about spring-data-jpa

[spring-projects-issues]

Nicholas Padilla commented

I'd really like to see this implemented as well. I don't like having to use ORM specific features and since I am using Spring Data for everything else it makes sense to use a "history" feature as well. I have the Audit set up working and now trying to formulate a plan for dealing with the history aspect of this.

In most use cases you will want to get all revisions of a particular entity, to display for end user viewing of the changes, not just a single revision. All other methods should return just the latest revision. Although, having an ability(as you have laid out) to get a specific revision to maybe update or roll back changes to a that revision would be helpful. Or maybe just providing a rollback function that will do the rollback for you would be even nicer.

Maybe we could create another Repository that is HistoricalRepository that we can add to the current entity repository or to a new HistoricalRepository that a new class would extend for the same entity. This way we can have a separation of concerns and not bloat a SimpleJpaRepository (or JpaRepository which already has lots of methods) with additional clutter. If an end user wants to perform all functions in the same class, that ability is still there but not required. I will be looking more at this next week, I'll pull down the spring data repo and see what this feature will take.

[spring-projects-issues]

Oliver Drotbohm commented

You might wanna take a look at the Spring Data Envers project and see in how far this actually helps you already

[spring-projects-issues]

Nicholas Padilla commented

Hey Oliver!

Thanks for the heads up! However, it looks like you are using a Hibernate specific implementation. I am using EclipseLink and am not sure if the mismatch will work. Hibernate is not really my first choice. Let me know if eclipselink will work with this module or not, that way I don't have to spend that time! :) If anything I will test it out and see if I can take it anywhere. If it fails then I will use it as reference code to implement an eclipselink specific variation.

EclipseLink uses session events to implement its history tracking: http://wiki.eclipse.org/Introduction_to_EclipseLink_Sessions_%28ELUG%29#Table_83-2.

[spring-projects-issues]

Oliver Drotbohm commented

Closing this as fixed as we have a Hibernate Envers specific implementation in place with the Spring Data Envers project. Adding additional implementations based on other JPA providers versioning infrastructure should be tracked with tickets in Spring Data Commons with requests (or even started implementations) for concrete implementations.

Marking this as fixed agains 1.2 GA as there will be a release of Spring Data Envers based on this Spring Data JPA version

[spring-projects-issues]

Oliver Drotbohm commented

Closing this as fixed as we have a Hibernate Envers specific implementation in place with the Spring Data Envers project. Adding additional implementations based on other JPA providers versioning infrastructure should be tracked with tickets in Spring Data Commons with requests (or even started implementations) for concrete implementations.

Marking this as fixed agains 1.2 GA as there will be a release of Spring Data Envers based on this Spring Data JPA version