]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commitdiff
fix typo in reference documentation
authorFederico Caselli <cfederico87@gmail.com>
Fri, 22 May 2020 22:11:46 +0000 (00:11 +0200)
committerFederico Caselli <cfederico87@gmail.com>
Fri, 22 May 2020 22:11:46 +0000 (00:11 +0200)
Change-Id: I5720635863f0d8a8ebfa4ddc51008bb93c1067b4

doc/build/changelog/migration_13.rst
lib/sqlalchemy/orm/query.py
lib/sqlalchemy/sql/selectable.py

index 78ac21fb540527ede5814a01528c646b9642b760..6e291335088e6b015f230644f9a0e62364c0ba90 100644 (file)
@@ -1672,7 +1672,7 @@ However, the current situation is that :class:`.Sequence` has been repurposed
 on SQL Server specifically in order to affect the "start" and "increment"
 parameters for the ``IDENTITY`` specification on a primary key column.  In order
 to make the transition towards normal sequences being available as well,
-using :class:.`.Sequence` will emit a deprecation warning throughout the
+using :class:`.Sequence` will emit a deprecation warning throughout the
 1.3 series.  In order to affect "start" and "increment", use the
 new ``mssql_identity_start`` and ``mssql_identity_increment`` parameters
 on :class:`_schema.Column`::
index 70b8a71e3e5a82062554e92e3403c45cc885c107..7719a551e1d2fd547948821fedaed650f5211690 100644 (file)
@@ -1599,7 +1599,7 @@ class Query(Generative):
 
             :meth:`_query.Query.with_statement_hint`
 
-            :meth:.`.Query.prefix_with` - generic SELECT prefixing which also
+            :meth:`.Query.prefix_with` - generic SELECT prefixing which also
             can suit some database-specific HINT syntaxes such as MySQL
             optimizer hints
 
index cc82c509b5325adedb9666ada017367ee454a0d5..85abbb5e063b18ff66b6a50250cc9158d34d3de1 100644 (file)
@@ -3838,7 +3838,7 @@ class Select(
 
             :meth:`_expression.Select.with_hint`
 
-            :meth:.`.Select.prefix_with` - generic SELECT prefixing which also
+            :meth:`.Select.prefix_with` - generic SELECT prefixing which also
             can suit some database-specific HINT syntaxes such as MySQL
             optimizer hints