summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2017-08-22 18:15:59 -0400
committerMike Bayer <mike_mp@zzzcomputing.com>2017-08-22 18:15:59 -0400
commitd8a80a35a0f117c7659c7a9c62e27994d3aadc01 (patch)
tree7ae6e75617dacf2d38090289fcc99a10b1d4c66a
parent2db525614371de011b2c65a41a8b342b15865f3c (diff)
downloadsqlalchemy-d8a80a35a0f117c7659c7a9c62e27994d3aadc01.tar.gz
- fix typos
Change-Id: Ibf8bc0e997ff989c7b0c16afad48a95414078052
-rw-r--r--doc/build/faq/connections.rst6
-rw-r--r--lib/sqlalchemy/dialects/mysql/base.py2
2 files changed, 6 insertions, 2 deletions
diff --git a/doc/build/faq/connections.rst b/doc/build/faq/connections.rst
index 40bef6a50..3c7175fe8 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 d6701aeae..0cffae389 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: