>> For connection pooling in ADO.Net a new database connection should be >> created each time a databse connection object is needed and the >> connection pool takes care of making connection re-use efficient. > > This is likely a good idea anyway (and is now at the end of my rather > lengthy TODO list).
Currently dblinq seems to work in this way: new IDbConnection() reads connection from static thread-safe ado .net pool (if ado provider implements pooling). IDbConnection.Dispose() issued by connection creator (dblinq or user who passes connection) returns connection to pool. So I don'nt undrestand what to do? Andrus. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" 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/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
