Hi,

I was trying to initialize the association by using HibernateCallBack for detached objects. However, I was seeing some update statements being fired even though I was just trying to reattach (lock) the object back to the current hibernate session within the HibernateTemplate. It looks like this was also related to the fact that the table has the version column inside. Am I missing something?

Hibernate version:3.2.4 sp1

Mapping documents:

Code between sessionFactory.openSession() and session.close():
final Object parent = theParent;
final Object child = theChild;
hibernateTemplate.execute(new HibernateCallback() {
public Object doInHibernate(Session session) throws HibernateException {
session.lock(parent, LockMode.NONE);
Hibernate.initialize(child);
return null;
}});


Full stack trace of any exception that occurs:

Name and version of the database you are using:

The generated SQL (show_sql=true):

Debug level Hibernate log excerpt:
Hibernate: update TABLE_A set version=?, CREATED_BY=? ... where ID=? and version=?



Problems with Session and transaction handling?

Read this: http://hibernate.org/42.html

Hibernate decides when to flush updates - I assume these are updates that have been made programmatically but have not yet been sent to the DB?

Not sure why the lock() call would do this, but it may be that Hibernate needs to flush all updates so that when it queries the version number to avoid optimistic lock failure it gets the up-to-date version number rather than the version number from before you started making changes.

I usually just accept that the flushing of changes to the DB will be unpredictable.

No, there's no update for the object. I was just trying to re-attach the object to the current session and initialize the associated collection.

I am seeing the same problem. Session.lock seems to be causing a update to be generated. I have a break point in my code and saveOrUpdate is never being called.