Use @event.Session.GetSession(EntityMode.Poco) instead. It will give you everything you need including the transaction so you won't need to enlist. Make sure you call flush on your child session as well.
On Jul 14, 3:16 pm, Marcus Kimpenhaus <kimpenh...@devil- engineering.de> wrote: > digged a little bit deeper into. the reason why update and delete are > doing well and insert doesn't seems to be all about batching. The > insert statement has useBatch = true. And that seems te mean that it > is processed on Commit?! both stored proc calls are fired immediately > against the database. > > Do I have any chance to get a stored prco being called at the > beginning and at the end of a roundtrip to the database? That's what I > need - it must not be accomplished by listeners. -- 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.
