Add the ability to control whether the session should be flushed, by adding a check against the FlushMode of the session.
For requests that perform read-only operations (such as Session.get() and Session.find()) against the database, flushing is unnecessary.

Flushing does a dirty check against all objects attached to the session and attempts a synchronization with the database if necessary.
This can be potentially very expensive as more objects are loaded into the session. It can also cause hibernate to
acquire locks on the database for objects attached to the session that the client had absolutely no intention to change.