repair doc warnings

Change-Id: I446105028539a34da90d6b8ae4812965cc398ee5
(cherry picked from commit c539ee35229b03d61f2a10e9f5ab613201341e19)

diff --git a/doc/build/changelog/changelog_14.rst b/doc/build/changelog/changelog_14.rst
index ef5e4e7f948d30051b755cda0baa3a93337b5455..9dc1cf91c1febc35849a794895cf79a93d06b7a4 100644 (file)
--- a/doc/build/changelog/changelog_14.rst
+++ b/doc/build/changelog/changelog_14.rst
@@ -155,7 +155,7 @@ This document details individual issue-level changes made throughout
         with a :class:`.Numeric` datatype would produce errors when attempting to
         reconcile the "autoincrement" column, preventing construction of the
         :class:`.Column` from using the :paramref:`.Column.autoincrement` parameter
-        as well as emitting errors when attempting to invoke an :class:`.Insert`
+        as well as emitting errors when attempting to invoke an :class:`_dml.Insert`
         construct.
 
 
@@ -195,7 +195,7 @@ This document details individual issue-level changes made throughout
         :tickets: 8073
 
         An informative error is raised for the use case where
-        :meth:`.Insert.from_select` is being passed a "compound select" object such
+        :meth:`_dml.Insert.from_select` is being passed a "compound select" object such
         as a UNION, yet the INSERT statement needs to append additional columns to
         support Python-side or explicit SQL defaults from the table metadata. In
         this case a subquery of the compound object should be passed.
@@ -233,8 +233,8 @@ This document details individual issue-level changes made throughout
 
         Fixed an issue where using :func:`.bindparam` with no explicit data or type
         given could be coerced into the incorrect type when used in expressions
-        such as when using :meth:`.ARRAY.Comparator.any` and
-        :meth:`.ARRAY.Comparator.all`.
+        such as when using :meth:`_types.ARRAY.Comparator.any` and
+        :meth:`_types.ARRAY.Comparator.all`.
 
 
     .. change::

diff --git a/doc/build/changelog/unreleased_14/7249.rst b/doc/build/changelog/unreleased_14/7249.rst
index 5d0cb658187242d51e945834bd60b18252d3672c..5244a65a2071fe32ca406dcd1d9d93f519ffdaa5 100644 (file)
--- a/doc/build/changelog/unreleased_14/7249.rst
+++ b/doc/build/changelog/unreleased_14/7249.rst
@@ -3,5 +3,5 @@
     :tickets: 7249
 
     Fixed issue where :class:`.TypeDecorator` would not correctly proxy the
-    ``__getitem__()`` operator when decorating the :class:`.ARRAY` datatype,
-    without explicit workarounds.
+    ``__getitem__()`` operator when decorating the :class:`_types.ARRAY`
+    datatype, without explicit workarounds.

diff --git a/doc/build/core/engines.rst b/doc/build/core/engines.rst
index c8af6626a3c9b5bda10fe5820cb9e077129f3c7a..91f6b1cabf90dc9eaa531e56d336604c7e77ae79 100644 (file)
--- a/doc/build/core/engines.rst
+++ b/doc/build/core/engines.rst
@@ -62,7 +62,7 @@ hostname, database name as well as optional keyword arguments for additional con
 In some cases a file path is accepted, and in others a "data source name" replaces
 the "host" and "database" portions.  The typical form of a database URL is:
 
-.. sourcecode:: plain
+.. sourcecode:: none
 
     dialect+driver://username:password@host:port/database
 
@@ -84,7 +84,7 @@ Below is an example of a URL that includes the password ``"kx@jj5/g"``, where th
 "at" sign and slash characters are represented as ``%40`` and ``%2F``,
 respectively:
 
-.. sourcecode:: plain
+.. sourcecode:: none
 
     postgresql+pg8000://dbuser:kx%40jj5%2Fg@pghost10/appdb
 

diff --git a/lib/sqlalchemy/dialects/mssql/base.py b/lib/sqlalchemy/dialects/mssql/base.py
index c3e69584a633d4b0741bae48ff3c0122791bd7db..f98df1c20ba458e4a572eb9cdaae778b397239fb 100644 (file)
--- a/lib/sqlalchemy/dialects/mssql/base.py
+++ b/lib/sqlalchemy/dialects/mssql/base.py
@@ -436,7 +436,7 @@ Valid values for ``isolation_level`` include:
 * ``SNAPSHOT`` - specific to SQL Server
 
 There are also more options for isolation level configurations, such as
-"sub-engine" objects linked to a main :class:`.Engine` which each apply
+"sub-engine" objects linked to a main :class:`_engine.Engine` which each apply
 different isolation level settings.  See the discussion at
 :ref:`dbapi_autocommit` for background.
 

diff --git a/lib/sqlalchemy/dialects/mysql/base.py b/lib/sqlalchemy/dialects/mysql/base.py
index 9e7ba4646b63902f24833765385aa372daf7892d..4b0a5e6c5e4cb62c2b49664fdfcfbfd3e2f12b36 100644 (file)
--- a/lib/sqlalchemy/dialects/mysql/base.py
+++ b/lib/sqlalchemy/dialects/mysql/base.py
@@ -241,7 +241,7 @@ the database connection will return true for the value of
 ``SELECT @@autocommit;``.
 
 There are also more options for isolation level configurations, such as
-"sub-engine" objects linked to a main :class:`.Engine` which each apply
+"sub-engine" objects linked to a main :class:`_engine.Engine` which each apply
 different isolation level settings.  See the discussion at
 :ref:`dbapi_autocommit` for background.
 

diff --git a/lib/sqlalchemy/dialects/postgresql/base.py b/lib/sqlalchemy/dialects/postgresql/base.py
index ae2f12d3fd4e751899e36966c1aa483f2cf24936..35a09cfa769d95e70f250a2445ff71137746a62e 100644 (file)
--- a/lib/sqlalchemy/dialects/postgresql/base.py
+++ b/lib/sqlalchemy/dialects/postgresql/base.py
@@ -178,7 +178,7 @@ To set using per-connection execution options::
             # ... work with transaction
 
 There are also more options for isolation level configurations, such as
-"sub-engine" objects linked to a main :class:`.Engine` which each apply
+"sub-engine" objects linked to a main :class:`_engine.Engine` which each apply
 different isolation level settings.  See the discussion at
 :ref:`dbapi_autocommit` for background.