Thanks for the pointer. Unfortunately, the implementation doesn't rely on
native database triggers.
There is only one things that could unlock the use of lifecycle for a legal
audit system : the abilty to catch modification on entity done outside the JVM.
I don't think this is possible => native
Hi,
Few pointers...
http://webspherepersistence.blogspot.com/2009/01/auditing-with-openjpa.html
-
Pinaki
--
View this message in context:
http://openjpa.208410.n2.nabble.com/JPA-for-portable-database-management-tp5134215p5142920.html
Sent from the OpenJPA Users mailing list arc
OK, let's imagine we'll have to do it.
How will we describe it in OpenJPA ?
Should we have some technical annotation like @NativeTrigger or should we have
higher level annotation like @Audit ?
The later had been done for Hibernate here : http://www.jboss.org/envers
Unfortunately it use lifecycle
I know what do you mean but I really need to do that from Java like the =
DBA would do in your scenario.
I would love to do that using annotation with OpenJPA mappingtool.
In fact native query are not portable by nature and also, trigger is =
more static than dynamic like database schema is.
That'
