On 1/7/2011 7:52 AM, Michael Bayer wrote:
the disconnect detection has to be implemented individually for each DBAPI for each backend. pymssql is not very frequently used so this would appear to be a missing message. We currently intercept:"Error 10054", "Not connected to any MS SQL server", "Connection is closed" not sure why you're getting something different - those values were added in March 2010, ultimately from an end-user, to support the new rewrite of pymssql.
FYI (Having nothing to do specifically with pymssql or SA), I ran into a similar problem with a server containing a connection pool. While the server was idle, the DBA restarted the SQL Server. The next access through one of the pooled connections got an error message that was very much nonspecific. After some digging, I was unable to identify any way to distinguish this case from other errors. I wound up gving up on the pool, and creating a new connection for each request.
-- Don Dwiggins Advanced Publishing Technology -- You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en.
