Hi Dietrich, Thanks for the reply - I replied last Friday but it seems to have disappeared into the mists of the internet.
> I have always noticed merge, save, and delete running the sql statement on > call. If you call them within the scope of a transaction, however, you can > always roll back the transaction to negate the changes. Well that it what I am seeing here too (insert generated when I call merge). I really wouldn't expect it to though because the flush mode is 'Never.' In this case I do not want to roll back the transaction - I am building up a domain object over multiple web requests and want to re- associate it with the current session so that I can rely on lazy loading. The ideal solution here would probably be to switch to some sort of session-per-conversation pattern but I simply do not have the time to change the architecture. regards, Jordan. -- 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.
