Hi, I've experienced an issue whereby when performing updates to an nhibernate 2.2 mapped object at the point of transaction commit the sql command issued by nhibernate leads to either a page lock or table lock being issued rather than the desired row lock(s). In a multithreaded environment this has lead to deadlock scenarios. I've used the default transaction isolation level.
I've currently found two ways of solving this problem: 1. Turn on snapshot isolation on the SQL Server database & then where needed set the transaction isolation level within nhibernate to snaphot. 2. Modify the nhibernate source code to issue update statements with rowlock included in the sql. I was wondering if this is an issue anyone else has experienced and if there is away of achieving a row lock by configuration rather than source code modification? Any help would be greatly appreciated. Thanks, Dave -- 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.
