Connection KIlled <> Connection.State=Closed?
387625Mar 3 2003 — edited Dec 6 2004I have a sample project using OLEDB .Net where whenever there is an Exception thrown from a database method call I check the Connection.State and if it is Closed I notify the users that they have been dropped and need to log in later.
I am now switchin to ODP .Net instead of OLEDB and when a connection error is thrown it no longer closes the Connections State. It is still set to Open. Is this a bug?
Do I need to do something else to determine the Connection State? Why have it there if it does not close when certain errors are thrown?
Can I capture if a connection is closed without searching for specific error messages in the OracleException Message?