Yes, it is a bug.
We should handle this scenario. What I don't understand is _why_.
I am pretty sure that this should generate the same logic as a rollback
does, and we are clearing things on rollback.

On Thu, May 6, 2010 at 3:19 PM, Davy Brion <[email protected]> wrote:

> Hey guys,
>
> i just ran into a weird issue with leaking connections due to using a
> TransactionScope without using an NH transaction...  i've described the
> problem here:
>
> http://davybrion.com/blog/2010/05/avoiding-leaking-connections-with-nhibernate-and-transactionscope/
>
> the thing is: is this a bug in NH or not? I mean... it might be due to bad
> usage, but if the usage scenario is bad, then NHibernate should probably
> warn against it instead of playing along and failing silently in some
> cases...
>
> thoughts?
>

Reply via email to