Hello Earlier today I commited a patch to ActiveRecord that restored the behaviour of SessionScope with respect to flushing. This change was crucial for a release because it prevents user from having to flush manually when using session scopes.
I also want to change TransactionScope to use FlushMode.Auto instead of FlushMode.Commit. This would be a breaking change, but it also standardizes flushing behaviour for all types of scopes. This helps especially in DDD since the transaction can be controlled outside of the model, with no manual flushes necessary. Additionally, there is no difference between code running in SessionScope and code running in a TransactionScope. Other ideas I'd love to see in 1.0, but that could also come in 1.1: - StatelessSessionScope - Event support (configuration/Windsor) - Adding hbm.xml files for hybrid AR/NH use. So what are your opinions on 1. changing TransactionScope and 2. releasing now or first completing NH2.0 support? -Markus --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
