Yup, no transactions (legacy, can't switch anytime soon) which is why
I didn't originally write any rollback framing... but I was still
getting the following error after MySQL raised a 2006 (until app
restart), and a quick peek at _handle_dbapi_exception seemed to
suggest that I needed to issue rollbacks even for non-transactional
database engines.
InvalidRequestError: Can't reconnect until invalid transaction is
rolled back
It goes without saying, but perhaps I've misunderstood something...
--diana
On Wed, Apr 28, 2010 at 10:52 AM, Chris Withers <ch...@simplistix.co.uk> wrote:
>
>> MySQL MyISAM, wait_timeout=28800
>
> You have no transactions, so I'm not sure why you're worrying about them...
> Switch to InnoDB if you want transactions...
>
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
