Hi again!

Since trigger support is inconsistent across various databases, I'd like to see if I could simulate triggers via Hibernate. I looked at the interceptors and event handlers, but they don't allow me to react to "nitty gritty" events. In other words, I want to get a notification when Hibernate executes an INSERT or DELETE, e.g. when a link table row is added or removed (I want to use this to keep an audit history of relationship changes).

Any suggestions?

Thanks!

Jen

hibernate 3x, event system
http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#objectstate-events

Thanks, but the event system is not fine-grained enough. I want to be notified when an actual INSERT SQL statement is executed, so I can track changes to link tables, not just entity objects.

you can audit history of relationship changes in object level. see
http://martinfowler.com/ap2/timeNarrative.html

Thanks for the pattern. Ideally, what I'd like to create an audit record whenever Hibernate creates or deletes a link table row -- I don't want to write this as custom persistence code.
This would be very easy with ON INSERT / ON DELETE triggers, but I want to be able to use a db like MySQL that doesn't support triggers that access other tables, so I'm looking for something like an interceptor...

Jen

We've implemented auditing in our application using the design proposed in Hibernate In Action (pages 340 - 347). We're quite happy with it except for one thing. As the originator of this thread has reported, there does not seem to be a good way to hook into modifications that are made to link tables. Our only option seems to be to model our many-to-many as 2 one-to-manys and create a POJO that maps directly to the link table. Yuk. I really like being able to manage the many-to-many without creating a specific class and mapping for the link. Does anyone have a better solution? If not, I'd like to request that a future version of Hibernate support this. And if a second edition of the book is forthcoming, I think this limitation is defniitely worth calling out.

Thanks,
Max