I'm a hibernate newbie and I have a question regarding direct HQL queries/inserts and versioning. I've been searching the web for anything related to this, but I can't seem to find anything that addresses this question.

I know that if I interact with hibernate using objects, that hibernate under the hoods will version things for me, and be able to detect if there was an update on the same row that I am currently updating. This is accomplished by hibernate checking the version column to see if the version number was incremented.

However, what about the case where I'm using a direct HQL query? For example, instead of something like

Transaction t = session.beginTransaction();
foo.setProperty("bar");
session.flush();
t.commit();
session.close();

what if instead I issued an HQL command something like

update foo set property='bar';

Instead of interacting with the actual object, I"m just basically updating the column in the database. Will hibernate still do the versioning automatically still, or will I need to implement this myself? If I need to implement this myself, will I need to use pessimistic locking, or can I still somehow use optimistic locking?

Hibernate will, by default, not update versions or timestamps. According to the documentation at http://www.hibernate.org/hib_docs/v3/re ... irect.html
you should be able to do


to force Hibernate to also update the version or timestamp.