]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
introduce "autobegin" concept for Connection
authorMike Bayer <mike_mp@zzzcomputing.com>
Thu, 26 Mar 2020 21:26:57 +0000 (17:26 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Thu, 26 Mar 2020 21:26:57 +0000 (17:26 -0400)
commitee1e1e2f5540a6e32986b1041db4dfd55894e68b
tree1c86cde57aef8603d12ca3935fa43cd042f99b11
parent2d4171ec8c85a468bdbdcf55e8d053b1586747ff
introduce "autobegin" concept for Connection

because engine.connect() and engine.begin() should feature
identical internal behavior, with the sole exception that
one rolls back and the end and the other commits at the end,
while also supporting execution options like transaction isolation level
at the connection level, include that engine.connect() will
return a connection that uses autobegin in the same way as the
session will.   This is solely to support the "begin" event
noting that a transaction is begun which is tracked on the
connection.    Behavior and design should be very similar to that
of the ORM session and "Transaction" should no longer be a very
explicit object.

Change-Id: I9c317d242ca7a435de0f17b1618355e29a10d1bc
doc/build/changelog/migration_20.rst