Inspired by Hibernate Envers, is it compatible?

[hoshsadiq]

So the readme says this is inspired by Hibernate Envers, does this mean it's also compatible with it? If I have a Hibernate based project with a Symfony2 project, will they work together?

[tolry]

What exactly do you mean by "compatible"? Having two applications using the same database, one hibernate, one doctrine and still being able to read and write to the EntityAudit? For this to work, EntityAutit's and Envers' database structure need to be completely the same. Since I didn' t create EntityAudit and haven't checked out Envers yet, I can not tell you that. You would probably have to setup an exemplary application of both types and give it a try.

But: in general, you don't want to have two applications to access the same database, but rather have a service layer in between. This way you can encapsulate your domain logic.

[hoshsadiq]

I completely agree with your statement, but such is the project I work on, and it's a big code base so I cannot simply change things. But yes, my question was basically if I enable this and Hibernate Envers, will they work as required, i.e. if doctrine audit one of the entries, will I be able to access it using Hibernate and vice versa? Anyway, we've opted for triggers since it's the best way to do for now.