On Jan 30, 2007, at 3:27 PM, Ian wrote:

what kind of application are you writing where an exception occurs, and the program continues to proceed normally ?

it would be a tall order for SA to implement "atomicity" for in- memory datastructure operations and add quite a bit of overhead and complexity to all cascade operations and many others. the usual pattern here is that you start over again and use a new Session. Here's how hibernate documents its own session (which recall sets up the basic model we are working from):

http://www.hibernate.org/hib_docs/v3/reference/en/html/ transactions.html#transactions-basics-issues

"Never use the anti-patterns session-per-user-session or session-per- application (of course, there are rare exceptions to this rule). Note that some of the following issues might also appear with the recommended patterns, make sure you understand the implications before making a design decision:"

"An exception thrown by Hibernate means you have to rollback your database transaction and close the Session immediately (discussed later in more detail). If your Session is bound to the application, you have to stop the application. Rolling back the database transaction doesn't put your business objects back into the state they were at the start of the transaction. This means the database state and the business objects do get out of sync. Usually this is not a problem, because exceptions are not recoverable and you have to start over after rollback anyway."