[Sqlalchemy-tickets] Issue #4218: is_active remains True after a database exception is thrown (zzze
Brought to you by:
zzzeek
Menu
▾
▴
[Sqlalchemy-tickets] Issue #4218: is_active remains True after a database exception is thrown (zzzeek/sqlalchemy)
|
From: Christophe B. <iss...@bi...> - 2018-03-19 18:32:56
|
New issue 4218: is_active remains True after a database exception is thrown https://bitbucket.org/zzzeek/sqlalchemy/issues/4218/is_active-remains-true-after-a-database Christophe Biocca: is_active should be False when a session is in a "partial rollback" state. The test case attached demonstrates that after catching an exception (one that should put the database in a "partial rollback" state AFAICT), session.is_active is still True. The kind of db exception doesn't seem to make a difference (IntegrityError was the original case I ran into). Postgres 10.3 Psycopg2 2.7.4 SQLAlchemy 1.2.5 |
