Does Hibernate provide an API call for determining if a persistable object is dirty?

I can always check for the id field being null for the new objects that are created before being written on the database, but I'd like to know if setXXX has been called for any field on objects loaded from the database.

I have a list of objects, and I'd like to iterate through those, and then for the ones that are new, called save() on those, and for the ones that are updated, I want to set up an audit record, and then call saveOrUpdate() on those.

Yes, its called Interceptor. The method you would be interested in is named onFlushDirty(). onFlushDirty gets passed three parallel arrays which indicate property state changes. Note however that there are some peculiarities with Interceptor usage for this purpose. The most frustrating being that changes to collection-based property of an entity will not cause the onFlushDirty method to be called (if some other properties also changed, it is called). But this may or may not be a big issue for you.

Check out the docs and see if this fits your needs.

What do you mean about this? I wrote a simple example with two classe a and b. a contains a collection of b.

I tried

and the flush() caused an onFlushDirty()!?!

Could you give a more detailed example, when changing a collection does not cause an onFlushDirty()?

Not sure how "load_a.setB(load_b)" constitutes changing a collection, but you know your app better than me. Also, I am assuming that save is not calling Session.save()

Consider:


where a has a collection of references to B. flush() will not cause an onFlushDirty() call to the interceptor here...

Uups, sorry!!!! I've tested with a many-to-one association, not with a collection. Have to be more careful the next time.

Hm, first I thought the problem Steve described above doesn't occur. Now I'm running into that behaviour and have to find a workaround :-(

Is there a simple workaround, that flush() causes Interceptor.onFlushDirty() to be called, without changing a non collection property to a "wrong" value?

Or will this behaviour be fixed in a later Hibernate version?

(What I want is, that a flush() causes a call of Interceptor.onFlushDirty(), even if only a collection of an object has changed).

There was a long discussion about this prior to 2.1 release (back on the old forums). As far as I know it was dropped for the time being.

I read the thread at the sourceforge forum, now. Mybe Gavin could tell us, what's the actual planning about this topic?

Thanks in advance.