best way to audit changes to collections

bleupen · **Posted:** Thu Jun 24, 2004 10:17 am

when a persistent collection is modified, Hibernate wont call the interceptor method onFlushDirty() unless the entity is versioned or a non-collection property has also been changed. i understand that this is by design but i don't understand the rationale behind the decision. i would happily use versioning if it didnt cripple batch updates. as it stands, i see no clear way to audit modifications to many-to-many bi-directional associations.

thoughts?

b

anthony · **Posted:** Thu Jun 24, 2004 10:42 am

Christian wrote
http://blog.hibernate.org/cgi-bin/blosx ... rytriggers

i don't know if this fit with your needs ...

bleupen · **Posted:** Thu Jun 24, 2004 11:37 am

anthony,

thank you for the link. your blog is interesting. how do you reconcile changes to third normal tables? e.g. what if you want to reconstruct the state of an entity, including all of its relationships (1.*, *.1, *.*), at a given moment in time?

b

anthony · **Posted:** Thu Jun 24, 2004 11:40 am

i think you have to use only the view... not the two source tables

i may not understand your question...

bleupen · **Posted:** Thu Jun 24, 2004 11:46 am

suppose you have two entities that share a many-to-many relationship. e.g.:

Code:

public class Person extends Persistent
{
   private Set departments;

   public get/setDepartments();
}

public class Department extends Persistent
{
   private Set people;

   public get/setPeople();
}

the people-departments association is mapped via a PersonDepartment third normal table (each row in this table will have a max version number of 1).

now suppose i want to answer the question "to what departments did Person XYZ belong to on June 5th 2003?". we can assume for argument's sake that we know Person XYZ's record was at version 5 on June 5th 2003.

b

christian · **Posted:** Thu Jun 24, 2004 12:01 pm

So, use the same pattern for the link table, with a trigger and a view.