On Fri, 2009-06-19 at 18:32 +0200, Giacomo Tesio wrote: > BUT, AFAIK, IDbConnection is open and closed by the DataContext just > when needed (on SubmitChanges for example, or when executing the > query). > > So it is short lived even if the DataContext is not.
Perhaps greyman can provide more details, but my interpretation of his statements was that using IDbConnection.Open() and IDbConnection.Close() did not make that IDbConnection instance resilient to intermittent connection errors (pulled Ethernet plug, etc.). I have no idea why this would be the case, though testing it should be simple enough -- start a DB request and kill your network connection while it's in progress. After your DataContext throws an exception (due to the DB not being around), restart your network connection and see if the DataContext is still usable. - Jon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
