I have a transaction that has more than one query stored internally by hibernate. It contains both updates and inserts. When flush() is called at the end of the transaction I want the queries to be executed in the order in which the session.insert() and session.update() were called. Right now Hibernate is collating all inserts and then all updates and flushing it in insert/update order.

Is there any way we could control Hibernate and specify the order in which the queries are executed? Any other way we could handle this scenario?

You could manually flush the session from time to time by calling

Thanks for the reply. This is one option we are currently looking at but this would severely affect the performance, as there would be multiple database calls. We want to avoid this scenario and do the flush only once.

I'm not sure if this really affects performance, because the number of sql statements sent to the database is the same in both cases, as long as you do not change the same objects over and over again.

(Note that hibernate itself by default calls flush every time before executing a query)

Hower, flushing very early may result in early database locks - so the probability of deadlocks may be increased.

We would like to do it at transaction level as otherwise Rollbacks would be difficult to keep track off. We read that the default order at flush time is Insert, Updates followed by Deletes for entity level processing.

What about using a StatelessSession? Stateless sessions do not cache anything and any insert/update/delete operation is immediately executed as SQL statement.

You can retrieve a stateless session from your SessionFactory:



But be cautious! Stateless sessions do not provider dirty checking, cascading of entity modifications and they bypass hibernate's event model and interceptors.

See chapter 13.3 of the hibernate documentation:
http://www.hibernate.org/hib_docs/v3/re ... esssession