PublicArchive/sqlalchemy
2
0
Fork 0
mirror of https://github.com/sqlalchemy/sqlalchemy.git synced 2026-05-26 10:32:33 -04:00
Code Issues Packages Projects Releases Wiki Activity

- fix typos

Browse Source 
Change-Id: Ibf8bc0e997ff989c7b0c16afad48a95414078052
(cherry picked from commit d8a80a35a0)
This commit is contained in:
Mike Bayer
2017-08-22 18:15:59 -04:00
parent b6412f6029
commit 6a8955f32b
2 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/build/faq/connections.rst
Vendored
+5 -1
View File
@@ -53,11 +53,15 @@ and replaced with a new connection when it is next checked out.
For the more general case of accommodating database restarts and other
temporary loss of connectivity due to network issues, connections that
are in the pool may be recycled in response to more generalized disconnect
detection techniques. The section :ref:`:ref:`pool_disconnects` provides
detection techniques. The section :ref:`pool_disconnects` provides
background on both "pessimistic" (e.g. pre-ping) and "optimistic"
(e.g. graceful recovery) techniques. Modern SQLAlchemy tends to favor
the "pessimistic" approach.
.. seealso::
:ref:`pool_disconnects`
Why does SQLAlchemy issue so many ROLLBACKs?
--------------------------------------------
lib/sqlalchemy/dialects/mysql/base.py
+1 -1
View File
@@ -42,7 +42,7 @@ be employed. See :ref:`pool_disconnects` for current approaches.
.. seealso::
:ref:`pool_disconnects` - Background on several techniques for dealing
with timed out connections as well as database restarts.
with timed out connections as well as database restarts.
.. _mysql_storage_engines: