Hi, Is there a good way to detect a problem with the database connection DbLinq is using and recover from it?
Testing with a MySQL database and switching it off while DbLinq is connected generates a MySqlException. Putting the app into a loop re- creating the DbLinq DataContext recovers from the situation. However is a MySqlException alone enough to assume the database is down? I imagine that exception could also be thrown for other non-connection related issues that don't require a new DataContext to be created. Plus the exception would then be different for each database. I had a look at myDataContext.Connection.Open after shutting down the MySQL database but it still flagged the connection as open. Thanks, Aaron --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
