From 0205ec7354fcc688bbc982280331b8343a6b2a2e Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Tue, 22 Aug 2017 18:15:59 -0400 Subject: [PATCH] - fix typos Change-Id: Ibf8bc0e997ff989c7b0c16afad48a95414078052 (cherry picked from commit d8a80a35a0f117c7659c7a9c62e27994d3aadc01) --- doc/build/faq/connections.rst | 6 +++++- lib/sqlalchemy/dialects/mysql/base.py | 2 +- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/build/faq/connections.rst b/doc/build/faq/connections.rst index 122f252781..9b0ba20cec 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 0aed1bea1f..e4599003f3 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: -- 2.47.3