Re: [Sqlalchemy-tickets] [sqlalchemy] #2536: ResourceClosedError can sometimes be raised instead of
Brought to you by:
zzzeek
From: sqlalchemy <mi...@zz...> - 2012-07-19 17:37:09
|
#2536: ResourceClosedError can sometimes be raised instead of more appropriate OperationalError ----------------------------------+------------------------------------ Reporter: jerdfelt | Owner: Type: defect | Status: new Priority: medium | Milestone: Component: access | Severity: no triage selected yet Resolution: | Keywords: Progress State: awaiting triage | ----------------------------------+------------------------------------ Comment (by jerdfelt): Sorry about missing the data to be inserted in the test case. Thankfully that was trivial. I wrote a test case using MySQLdb as well and both raised OperationalError for me, which is why I reported the bug here. It's quite possible that I'm using MySQLdb differently than SQLAlchemy does which results in different failures. I'm curious to see your test case and figure out why it's different than my test case. -- Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2536#comment:3> sqlalchemy <http://www.sqlalchemy.org/> The Database Toolkit for Python |