Hi

I'm calling the following line of code



For some strange reason, when Hibernate executes this line, rather than generating a 'select' for RefLabel, it actually executes an update, on a completely different object. The object it tries to do an update on is mapped OK (my JUnit tests can use it fine).

Anyone know under which circumstances Hibernate might do this wierd behaviour?

Thanks

Hi richardgundersen,

With in the transaction scope if any thing modified in persistent object then hibernate try to synchronies with DB.That cause update statement. So be careful when you are handling any persistent

Yep, in fact I fixed it just before I saw your message. It's down to this line of code:

getHibernateTemplate().setFlushMode(HibernateAccessor.FLUSH_EAGER);

I had updated the other object so it was dirty (but not ready for saving). So, when I did my read, it saw that the object was dirty and tried to persist it (which caused me problems because it wasn't ready to save).

The fix was to move the read statement to be the first line of code, and then after that I could modify my object and not worry about it being persisted in a half-baked state.

The Hibernate debug was very useful because it showed me the following detail



Although having debug on EVERYTHING in Hibernate really really slows things down :)

Thanks for the reply

Hi richardgundersen,

It is good to see that you have solved problem.