Hi Andrus,
I was experimenting with a TransactionFilter, which like the
DataContextFilter was trying to provide a carefree transaction around
web requests. I see that this is not going to work with transactions
as they are bound to resources. The use case was handling the
situation where the app
BTW, if there's no commit or rollback, and the transaction stays open
indefinitely, this would result in quick connection pool exhaustion.
So why would you do that?
Andrus
On Mar 9, 2008, at 7:19 PM, Andrus Adamchik wrote:
This could be a DB artifact. E.g. with MySQL MyISAM tables. Which DB
This could be a DB artifact. E.g. with MySQL MyISAM tables. Which DB
are you using?
Andrus
On Mar 8, 2008, at 5:53 AM, Malcolm Edgar wrote:
I have been playing around this in a web context, and what I am
finding with a user created Transaction, if the DataContext commits
the changes, unless
