diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2017-04-03 17:25:26 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2017-04-03 21:13:08 -0400 |
| commit | 9609f5ffb52ce8a4969059e299773ac7176dbb0d (patch) | |
| tree | 2baa750e58f1b6df000588e9a63188ff29cfab77 /lib/sqlalchemy/ext/mutable.py | |
| parent | d2c733742f2800264950045905a55e5fc9494a8b (diff) | |
| download | sqlalchemy-9609f5ffb52ce8a4969059e299773ac7176dbb0d.tar.gz | |
ResultProxy won't autoclose connection until state flag is set
Changed the mechanics of :class:`.ResultProxy` to unconditionally
delay the "autoclose" step until the :class:`.Connection` is done
with the object; in the case where Postgresql ON CONFLICT with
RETURNING returns no rows, autoclose was occurring in this previously
non-existent use case, causing the usual autocommit behavior that
occurs unconditionally upon INSERT/UPDATE/DELETE to fail.
Change-Id: I235a25daf4381b31f523331f810ea04450349722
Fixes: #3955
(cherry picked from commit 8ee363e4917b0dcd64a83b6d26e465c9e61e0ea5)
(cherry picked from commit f52fb5282a046d26b6ee2778e03b995eb117c2ee)
Diffstat (limited to 'lib/sqlalchemy/ext/mutable.py')
0 files changed, 0 insertions, 0 deletions