Well much to my fury, after wasting a full day's work after discovering this, it appears it was a false positive. It no longer passes, and I cannot see why. So changing the transaction strategy does not solve the problem(s). :(
Regards, John. On Wednesday, April 11, 2012 12:45:23 PM UTC+1, John T wrote: > > If anyone is still interested, I have discovered that configuring my > SessionFactory to use the AdoNetWithDistributedTransactionFactory > TransactionStrategy has resolved my issue(s) in this thread. > > When explicitly using this strategy I do *not* need to call > Session.BeginTransaction() and the earlier test passes. It also commits on > TransactionScope.Complete(); > > I am not yet aware if there is still a connection leak as according to > NH-2107 in the issue log, however. > > Regards, > John. > > On Tuesday, April 10, 2012 11:49:10 AM UTC+1, John T wrote: >> >> Hi guys, >> >> I've hit a problem where we have a case that we are creating an >> entity, saving it, then Query<T>()ing for it from cache and modifying >> it. I.e. not flushing in between the initial Save() and Query(). >> >> However, as I understand from a now quite old article[1] on Ayende's >> blog that this is "not possible" unless we explicity use Get()/Load(). >> >> Has the situation improved since then, or is the same restriction >> still in place? >> >> Many thanks, >> John. >> >> [1] >> http://ayende.com/blog/3988/nhibernate-the-difference-between-get-load-and-querying-by-id > > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/pkLS5Qv7t_0J. 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.
