Thanks for this. As an update, I put in code that notifies me when an error
occurs. The real cause of this seems to still be the 'MySQL has gone away'
error. This occurs in various places, always as the first DB call in a
request (obviously).
Is my understanding correct that in order to solve
On Nov 1, 2011, at 5:49 PM, Benjamin Sims wrote:
Thanks for this. As an update, I put in code that notifies me when an error
occurs. The real cause of this seems to still be the 'MySQL has gone away'
error. This occurs in various places, always as the first DB call in a
request
Hi all,
I'm seeing this error intermittently in my application since switching to
MySQL - it occurs on several different pages and I can't track down why:
StatementError: Can't reconnect until invalid transaction is rolled back
(original cause: InvalidRequestError: Can't reconnect until invalid
On Oct 31, 2011, at 8:45 AM, Benjamin Sims wrote:
Hi all,
I'm seeing this error intermittently in my application since switching to
MySQL - it occurs on several different pages and I can't track down why:
StatementError: Can't reconnect until invalid transaction is rolled back
I suspect that my understanding of both threading and Sessions is going to
be found pretty wanting here; I've basically just lifted things from
Pyramid/SQLAlchemy examples.
My understanding is that the framework handles threading, and that based on
examples and
On Oct 31, 2011, at 12:56 PM, Benjamin Sims wrote:
I suspect that my understanding of both threading and Sessions is going to be
found pretty wanting here; I've basically just lifted things from
Pyramid/SQLAlchemy examples.
My understanding is that the framework handles threading, and
