On Jul 15, 2007, at 7:21 PM, SamDonaldson wrote:
I haven't done any research on the mysql end yet but my question is,
why not disable the wait_timeout option on the mysql end to avoid such
connection closing from the server side. Wouldn't this problem go
away all together? Why would you
On Jul 15, 2007, at 6:33 PM, SamDonaldson wrote:
Ok. This did not work and I dug this thread where you had a
discussion on this. It seems like this was fixed in sqlalchemy and
you were calling rollback twice which caused this issue.
On Jul 15, 1:02 am, SamDonaldson [EMAIL PROTECTED] wrote:
Not to ask to many questions here but isn't there a standard value for
this? I mean, who would want their db connections to close
unexpectedly like this, especially on a live site? Is there a value
you recommend because this is
Ok. This did not work and I dug this thread where you had a
discussion on this. It seems like this was fixed in sqlalchemy and
you were calling rollback twice which caused this issue.
http://groups.google.com/group/sqlalchemy/browse_thread/thread/9412808e695168ea/c31f5c967c135be0?lnk=raot
I haven't done any research on the mysql end yet but my question is,
why not disable the wait_timeout option on the mysql end to avoid such
connection closing from the server side. Wouldn't this problem go
away all together? Why would you ever want to close idle connections
in such a way? If
use the pool_recycle argument as described here:
http://www.sqlalchemy.org/trac/wiki/
FAQ#MySQLserverhasgoneawaypsycopg.InterfaceError:connectionalreadyclosed
On Jul 14, 2007, at 8:15 PM, SamDonaldson wrote:
Hello group,
I'm having an issue with my site where I get the following error if
