]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
projects / thirdparty / sqlalchemy / sqlalchemy.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ed735af) | patch
Don't call rollback on DBAPI connection that's "closed"
authorMike Bayer <mike_mp@zzzcomputing.com>
Sun, 14 Oct 2018 19:55:46 +0000 (15:55 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Sun, 14 Oct 2018 23:17:40 +0000 (19:17 -0400)
commit92c20be2c244c98735cdf91d747a9227b58b9854
treed3eaeb23e494fff23d94afb25c8891a1da8ccda8tree | snapshot
parented735af55d2c863cbe7cfde7b4ef3a9cda7c0733commit | diff
Don't call rollback on DBAPI connection that's "closed"

Use the existence of ConnectionRecord.connection to estimate
that this connection is likely closed, and if so, don't
try to call "rollback" on it.  This rollback is normally harmless
but is causing segfaults in mysqlclient due to
https://github.com/PyMySQL/mysqlclient-python/issues/270.

Change-Id: I1d7c5f5a520527d8268b6334795c2051f7ceeea6
(cherry picked from commit a8781b51b4039eee56791b9dbfdee183f7a5b797)
lib/sqlalchemy/testing/engines.py diff | blob | blame | history
Mirror of https://github.com/sqlalchemy/sqlalchemy.git