Set up absolute references for create_engine and related

includes more replacements for create_engine(), Connection,
disambiguation of Result from future/baked

Change-Id: Icb60a79ee7a6c45ea9056c211ffd1be110da3b5e

1 files changed, 12 insertions, 8 deletions

diff --git a/lib/sqlalchemy/sql/dml.py b/lib/sqlalchemy/sql/dml.py
index bc800de42..4ed01375e 100644
--- a/lib/sqlalchemy/sql/dml.py
+++ b/lib/sqlalchemy/sql/dml.py
@@ -345,7 +345,8 @@ class UpdateBase(
 
         Upon execution, the values of the columns to be returned are made
         available via the result set and can be iterated using
-        :meth:`.ResultProxy.fetchone` and similar.   For DBAPIs which do not
+        :meth:`_engine.ResultProxy.fetchone` and similar.
+        For DBAPIs which do not
         natively support returning values (i.e. cx_oracle), SQLAlchemy will
         approximate this behavior at the result level so that a reasonable
         amount of behavioral neutrality is provided.
@@ -546,7 +547,8 @@ class ValuesBase(UpdateBase):
               True, indicating that the statement will not attempt to fetch
               the "last inserted primary key" or other defaults.  The
               statement deals with an arbitrary number of rows, so the
-              :attr:`.ResultProxy.inserted_primary_key` accessor does not
+              :attr:`_engine.ResultProxy.inserted_primary_key`
+              accessor does not
               apply.
 
            .. versionchanged:: 1.0.0 A multiple-VALUES INSERT now supports
@@ -682,7 +684,8 @@ class ValuesBase(UpdateBase):
         added to any existing RETURNING clause, provided that
         :meth:`.UpdateBase.returning` is not used simultaneously.  The column
         values will then be available on the result using the
-        :attr:`.ResultProxy.returned_defaults` accessor as a dictionary,
+        :attr:`_engine.ResultProxy.returned_defaults` accessor as a dictionary
+        ,
         referring to values keyed to the :class:`_schema.Column`
         object as well as
         its ``.key``.
@@ -712,7 +715,7 @@ class ValuesBase(UpdateBase):
         3. It can be called against any backend.  Backends that don't support
            RETURNING will skip the usage of the feature, rather than raising
            an exception.  The return value of
-           :attr:`.ResultProxy.returned_defaults` will be ``None``
+           :attr:`_engine.ResultProxy.returned_defaults` will be ``None``
 
         :meth:`.ValuesBase.return_defaults` is used by the ORM to provide
         an efficient implementation for the ``eager_defaults`` feature of
@@ -729,7 +732,7 @@ class ValuesBase(UpdateBase):
 
             :meth:`.UpdateBase.returning`
 
-            :attr:`.ResultProxy.returned_defaults`
+            :attr:`_engine.ResultProxy.returned_defaults`
 
         """
         self._return_defaults = cols or True
@@ -919,7 +922,8 @@ class Insert(ValuesBase):
            True, indicating that the statement will not attempt to fetch
            the "last inserted primary key" or other defaults.  The statement
            deals with an arbitrary number of rows, so the
-           :attr:`.ResultProxy.inserted_primary_key` accessor does not apply.
+           :attr:`_engine.ResultProxy.inserted_primary_key`
+           accessor does not apply.
 
         """
 
@@ -1060,7 +1064,7 @@ class Update(DMLWhereBase, ValuesBase):
           the ``default`` keyword will be compiled 'inline' into the statement
           and not pre-executed.  This means that their values will not
           be available in the dictionary returned from
-          :meth:`.ResultProxy.last_updated_params`.
+          :meth:`_engine.ResultProxy.last_updated_params`.
 
         :param preserve_parameter_order: if True, the update statement is
           expected to receive parameters **only** via the
@@ -1185,7 +1189,7 @@ class Update(DMLWhereBase, ValuesBase):
         ``default`` keyword will be compiled 'inline' into the statement and
         not pre-executed.  This means that their values will not be available
         in the dictionary returned from
-        :meth:`.ResultProxy.last_updated_params`.
+        :meth:`_engine.ResultProxy.last_updated_params`.
 
         .. versionchanged:: 1.4 the :paramref:`_expression.update.inline`
            parameter