Depends on driver and database. TransactionScope uses IsolationLevel.Unspecified, so there is no locking at all unless you have version properties on your AR classes.
As a work-around, you cold specify default IsolationLevel to Serializable in TransactionScope.cs line 99, so the driver uses pessimistic locking. If you do so make sure you have tests available to look for deadlocks etc. -Markus 2011/2/19 raghavsri <[email protected]>: > > Hi, > Please anybody can tell me ,by default what kind of locking mechanism > is provided by the castle active record,when save or create operation > is performed in a transaction scope. > > Thanks in advance > Regards > > -- > 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. > > -- 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.
