Being relatively new to hibernate, I never stop reading the reference manual. Today I found the following in section 7.8 (Flushing Sessions):


Could someone just help me to get things clear: I thought that sessions can be considered as logical transactions. I planned to use sessions exactly like this. E.g. a user makes changes to an object through an UI. On user commit I would flush the session, on user abort, I would discard the session hopefully hibernate acts like I think it acts.

Is this scenario coherent with hibernate architecture or may the session be flushed at arbitrary moments without explicitely flushing it?

Thanks for your help,

Peter

You also need to commit transaction then. See "7.9. Ending a Session" for details. For your application this should work fine - you open session, user does whatever he wants and when he clicks "finish" you flush session, commit transaction.

Session may also be flushed by Hibernate when you call session.find() method.

[/quote]

Well not really. Before any query, Hibernate need to flush previous changes to objets to preserve consistency of query result (would be very hard/impossible otherwise).
So you cannot suppose that all you've done can be executed or discarded by the session.flush() method.

Keeping transaction consistency is done via DB transaction.