Hello, I'm here with a doubt about a procedure with regard to Transactions use, when we perform a Session.Get. According to a post I read of Ayende Rahien, we must use Transactions allways including in Session.Get. It happens that I have a situation at hand that I eventually have to pick twice the same entity data, during the same Session. Of course, if I don't use Transactions everything goes fine and I can retrieve the entity data, but if I use, when I commit the second Session.Get of the same data, the NHibernate gives the following error:
"Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) " I've tried all IsolationLevel available with same results, and have the Locking Session.Get placed to LockMode.NONE. The error message makes no sense (at least for me) since there was no update or delete, before or between Session.Get's, and if there a mapping error that should have arisen in the first Session.Get. Is this a Bug? I can't use Tansactions in this conditions? Tia, Jorge Mota -- 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.
