summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndy Garfield <andyjgarfield@gmail.com>2022-11-15 11:28:58 -0500
committerGitHub <noreply@github.com>2022-11-15 11:28:58 -0500
commit36954a3dbb3a528d81c24db6b8698ba1e48d7cb2 (patch)
treeb7babc5c373692cda55e0441dcb48450f53b186e
parent9237bf15e612ba82555444751bd69dc2a831e7f4 (diff)
downloadsqlalchemy-36954a3dbb3a528d81c24db6b8698ba1e48d7cb2.tar.gz
Small tutorial rewording
The language is this sentence took me a few reads to understand. This is just a rewording.
-rw-r--r--doc/build/tutorial/dbapi_transactions.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/build/tutorial/dbapi_transactions.rst b/doc/build/tutorial/dbapi_transactions.rst
index 00178936b..d40aaf5b8 100644
--- a/doc/build/tutorial/dbapi_transactions.rst
+++ b/doc/build/tutorial/dbapi_transactions.rst
@@ -479,7 +479,7 @@ the block with a "commit as you go" commit.
.. tip:: The :class:`_orm.Session` doesn't actually hold onto the
:class:`_engine.Connection` object after it ends the transaction. It
gets a new :class:`_engine.Connection` from the :class:`_engine.Engine`
- when executing SQL against the database is next needed.
+ the next time it needs to execute SQL against the database.
The :class:`_orm.Session` obviously has a lot more tricks up its sleeve
than that, however understanding that it has a :meth:`_orm.Session.execute`