I have the following issue where Foo is using hibernate's automatic versioning:


Foo foo = new Foo();
// Inserts new Foo object with version 0 as expected
foo = session1.saveOrUpdate(foo);

// The following line revs the version of foo to 1 and Session.isDirty()
// will return true even though *no* modifications have been made
// to foo since the first save.
// Why???
foo = session2.saveOrUpdate(foo);


Does hibernate blindly update the version on objects attached to a session via saveOrUpdate()? Even when I have versioing turned off subsequent calls to saveOrUpdate() with an unchanged foo object would still cause session.isDirty() to be true. Why is this? All I want to do is detect whether my remote object has been modified when the user attempts a save. Is there a better best practice to do this? What am I missing here?

Thanks,
Edward

This is the correct behavior, hibernate does not know the current objectb state in DB.
If you want hibernate to do a select before actually updating, use


NB: in most case, the default value is better

I would have expected saveOrUpdate() to already do a select. If not, how does the saveOrUpdate() method know whether to do an INSERT or UPDATE into the database?

edward

Hum, this is a reference guide and a FAQ question. Just a hint unsaved-value