You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 7, 2020. It is now read-only.
EDIT: I'm currently working on some code that uses MySQLdb and I ran into an issue with a connection closing during processing, but the query continued on the database server.
For another database technology suffering from the same issue, we just defined a keep alive value on the Unix socket. However, I didn't see anything with MySQLdb/_mysql that would help.
Is there a way to use PySQLPool to do a keep alive on MySQLdb connections?
UPDATE: I verified on the database server that the wait/interactive timeouts are already set large (28800). I just need to confirm where and where the disconnect is happening.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
EDIT: I'm currently working on some code that uses MySQLdb and I ran into an issue with a connection closing during processing, but the query continued on the database server.
For another database technology suffering from the same issue, we just defined a keep alive value on the Unix socket. However, I didn't see anything with MySQLdb/_mysql that would help.
Is there a way to use PySQLPool to do a keep alive on MySQLdb connections?
UPDATE: I verified on the database server that the wait/interactive timeouts are already set large (28800). I just need to confirm where and where the disconnect is happening.
The text was updated successfully, but these errors were encountered: