LIke you said, the core of the issue is that AR scopes were modeled at a time when NHibernate didn't require mandates for updates. Since it does now, SessionScopes are out of date and cannot be used to reliably update data without violating NHib requirements. I have always used Rhino Transactions and UoW since it is based on that model, but it would be nice if AR followed that model to be consistent.
On Mon, Nov 3, 2008 at 7:25 AM, Markus Zywitza <[EMAIL PROTECTED]>wrote: > 2008/11/3 [EMAIL PROTECTED] [EMAIL PROTECTED] > >> @Markus: Well, then what's the point of having a TransactionScope? If >> SessionScope can handle it all? >> > The SessionScope does not have methods to explicitly commit or rollback > transactions. It uses an implicit transaction because NH2 requires it. > SessionScope is sufficient for simple CRUD-operations where only one object > is changed. > > The SessionScope is a remain from NH1.2 where transactions were optional. > In the long run we need to integrate another UoW-Concept that plays more > nicely with NH2. But this is one of the points I plan for AR 2.0 rather than > 1.x. > > -Markus > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
