summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2021-02-15 11:21:41 -0500
committerMike Bayer <mike_mp@zzzcomputing.com>2021-02-15 11:22:13 -0500
commit0698992bfd5eaa5d2fe99e279589c3f5819dc7d7 (patch)
tree5abdabb1a0272a0506c3b0374c4c129e41ce2c6b
parent2c1ab1304ecd70680f04fd9a7ecc75c37d4de4ea (diff)
downloadsqlalchemy-0698992bfd5eaa5d2fe99e279589c3f5819dc7d7.tar.gz
fix repeated footnote
Change-Id: Ibd8239907c3cf747d0d9a0fb670e37c9913871f8
-rw-r--r--doc/build/tutorial/data.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/build/tutorial/data.rst b/doc/build/tutorial/data.rst
index 5da8b8667..d006a9f85 100644
--- a/doc/build/tutorial/data.rst
+++ b/doc/build/tutorial/data.rst
@@ -1870,7 +1870,7 @@ Parameter Ordered Updates
Another MySQL-only behavior is that the order of parameters in the SET clause
of an UPDATE actually impacts the evaluation of each expression. For this use
case, the :meth:`_sql.Update.ordered_values` method accepts a sequence of
-tuples so that this order may be controlled [1]_::
+tuples so that this order may be controlled [2]_::
>>> update_stmt = (
... update(some_table).
@@ -1883,7 +1883,7 @@ tuples so that this order may be controlled [1]_::
{opensql}UPDATE some_table SET y=:y, x=(some_table.y + :y_1)
-.. [1] While Python dictionaries are
+.. [2] While Python dictionaries are
`guaranteed to be insert ordered
<https://mail.python.org/pipermail/python-dev/2017-December/151283.html>`_
as of Python 3.7, the