Hibernate version:2.13

We are using some code that is explicitly flushing - which we have seen takes a while - which makes sense.

We are not currently using a transaction in the instance, but instead

//session.flush(); --This taking a while for a relatively simple operation
session.connection().commit();

However when we access the db from another source we cannot see the records, but this could be that Hibernate has not flushed it's data yet.

Can someone explain the difference between commiting as above and using a transaction?

Transaction trans = session.beginTransaction();
....
trans.commit();

Flush tell hibernate to send any unit-of-work operations to the database, eg, execute outstanding SQL operations. Obviously, the flush needs to be performed (where Hibernate will automatically perform a flush in various situations) within the transaction boundary. The transaction can then be commited or rolledback depending again on success or otherwise or the use case. Don't use the JDBC driver directly for the transaction commit as it could cause the transaction manager to get out of sync. The Hibernate documentation clearly defines the transaction framework you should apply in your code, eg,



The above code is all that you need. The tx.commit will perform the flush for you.

Thanks David for confirming that.

Will use the full transaction consistently and check that that is ok.

This should offer some performance improvements I guess as Hibernate can then flush of it's accord. What are your views on this?

Thanks