Although I'm aware of this "feature" for ADO exceptions, I'm curious as to why. I know this debate has been had before but I've never seen it come to a conclusion.
Why is the session unusable after a "restartable" database errors such as timeout, deadlock, connection failure etc ? These are scenarios where, as far as I am aware, the "best practice" is to do an immediate retry as there is actually nothing wrong (as far as we know at this point) with the business data. Stale state is an obvious example as to where the session is indeed unusable and must be replaced. Why does NH make the session usable, and can it be changed to that in these types of cases the session is reusable so all the programmer has to do is retry the Flush/Commit etc. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
