Separate the spring data envers to work with a database separate from the main one

[sedrac-slc]

How to configure Spring Data Envers to use a separate database for auditing and thus avoid multiple connections to the main database. I have been trying to get past this situation and cannot find a simple solution, so I am presenting this situation, imagining that I am not the only one in this situation.

[schauder]

I don't think this can be done, since Envers is tied to Hibernate and its EntityManager, which is tied to its database connection. In any case the first step would be to find a way to configure Envers in the desired way, which would be something to discuss with the Hibernate team.

BTW: Envers doesn't create an extra database connection to your database, it uses the one Hibernate is already using.

[sedrac-slc]

I don't think this can be done, since Envers is tied to Hibernate and its EntityManager, which is tied to its database connection. In any case the first step would be to find a way to configure Envers in the desired way, which would be something to discuss with the Hibernate team.

BTW: Envers doesn't create an extra database connection to your database, it uses the one Hibernate is already using.

Yes, what I am suggesting is to have this possibility of connecting an extra database to avoid many operations in the main database. From what you said, I realise that it may not be such a simple case to resolve because of the dependence on Hibernate. Clearly, Spring Data Envers was not designed for this scenario, but perhaps the new versions can support it.

[schauder]

Spring Data JPA and Spring Data Envers are just a layer on JPA implementations (like Hibernate) and Envers (also from the Hibernate team). So this kind of thing has to be done by them first. Then we can consider integrating it and making it nice to use.