Hi, The scenario is as follows: We have an entity mapped to an Oracle database, and it is using a sequence as identity. When working with a standard NHibernate transaction everything works fine. But when we use TransactionScope (entering a distributed transaction) we have a strange problem.
It seems that the Session doesn't flush changes correctly in this scenario. That is, we save a new Employee object to the database, and then load all the employees. The new employee won't be in that collection - we have to explicitly call Session.Flash(). Note, this happens only in this specific scenario: when not using sequence as identity, or when not using TransactionScope, everything works as expected. Has anybody encountered this issue before? Is there a solution? Thanks, Doron -- 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.
