From: Mike Bayer Date: Tue, 22 Aug 2017 22:15:59 +0000 (-0400) Subject: - fix typos X-Git-Tag: rel_1_1_14~16 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6a8955f32bfbe0ace80efc6770003affe10ded6c;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git - fix typos Change-Id: Ibf8bc0e997ff989c7b0c16afad48a95414078052 (cherry picked from commit d8a80a35a0f117c7659c7a9c62e27994d3aadc01) --- diff --git a/doc/build/faq/connections.rst b/doc/build/faq/connections.rst index 40bef6a50a..3c7175fe85 100644 --- a/doc/build/faq/connections.rst +++ b/doc/build/faq/connections.rst @@ -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? -------------------------------------------- diff --git a/lib/sqlalchemy/dialects/mysql/base.py b/lib/sqlalchemy/dialects/mysql/base.py index fdca42fed3..5ccdb1e17b 100644 --- a/lib/sqlalchemy/dialects/mysql/base.py +++ b/lib/sqlalchemy/dialects/mysql/base.py @@ -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: