Commits

Mike Bayer  committed d5ca6b4

update sqla links for 0.8 docs

  • Participants
  • Parent commits 0ed2080

Comments (0)

Files changed (3)

File alembic/environment.py

         If the :meth:`.is_offline_mode` function returns ``True``,
         then no connection is needed here.  Otherwise, the
         ``connection`` parameter should be present as an
-        instance of :class:`sqlalchemy.engine.base.Connection`.
+        instance of :class:`sqlalchemy.engine.Connection`.
 
         This function is typically called from the ``env.py``
         script within a migration environment.  It can be called
         multiple times for an invocation.  The most recent
-        :class:`~sqlalchemy.engine.base.Connection`
+        :class:`~sqlalchemy.engine.Connection`
         for which it was called is the one that will be operated upon
         by the next call to :meth:`.run_migrations`.
 
         General parameters:
 
-        :param connection: a :class:`~sqlalchemy.engine.base.Connection`
+        :param connection: a :class:`~sqlalchemy.engine.Connection`
          to use
          for SQL execution in "online" mode.  When present, is also
          used to determine the type of dialect in use.
          will be consulted during autogeneration.  The tables present
          will be compared against
          what is locally available on the target
-         :class:`~sqlalchemy.engine.base.Connection`
+         :class:`~sqlalchemy.engine.Connection`
          to produce candidate upgrade/downgrade operations.
 
         :param compare_type: Indicates type comparison behavior during
           the output stream, as rendered by the
           target backend (e.g. SQL Server would
           emit ``BEGIN TRANSACTION``).
-        * Otherwise, calls :meth:`sqlalchemy.engine.base.Connection.begin`
+        * Otherwise, calls :meth:`sqlalchemy.engine.Connection.begin`
           on the current online connection, which
-          returns a :class:`sqlalchemy.engine.base.Transaction`
+          returns a :class:`sqlalchemy.engine.Transaction`
           object.  This object demarcates a real
           transaction and is itself a context manager,
           which will roll back if an exception
 
         Note that a custom ``env.py`` script which
         has more specific transactional needs can of course
-        manipulate the :class:`~sqlalchemy.engine.base.Connection`
+        manipulate the :class:`~sqlalchemy.engine.Connection`
         directly to produce transactional state in "online"
         mode.
 
         """Return the current 'bind'.
 
         In "online" mode, this is the
-        :class:`sqlalchemy.engine.base.Connection` currently being used
+        :class:`sqlalchemy.engine.Connection` currently being used
         to emit SQL to the database.
 
         This function requires that a :class:`.MigrationContext`

File alembic/migration.py

         This is a factory method usually called
         by :meth:`.EnvironmentContext.configure`.
 
-        :param connection: a :class:`~sqlalchemy.engine.base.Connection`
+        :param connection: a :class:`~sqlalchemy.engine.Connection`
          to use for SQL execution in "online" mode.  When present,
          is also used to determine the type of dialect in use.
         :param url: a string database url, or a
         """Return the current "bind".
 
         In online mode, this is an instance of
-        :class:`sqlalchemy.engine.base.Connection`, and is suitable
+        :class:`sqlalchemy.engine.Connection`, and is suitable
         for ad-hoc execution of any kind of usage described
         in :ref:`sqlexpression_toplevel` as well as
         for usage with the :meth:`sqlalchemy.schema.Table.create`

File alembic/operations.py

          and :class:`~.sqlalchemy.schema.Index` objects.
         :param schema: Optional schema name to operate within.
         :param \**kw: Other keyword arguments are passed to the underlying
-         :class:`.Table` object created for the command.
+         :class:`sqlalchemy.schema.Table` object created for the command.
 
         """
         self.impl.create_table(
          .. versionadded:: 0.4.0
 
         :param \**kw: Other keyword arguments are passed to the underlying
-         :class:`.Table` object created for the command.
+         :class:`sqlalchemy.schema.Table` object created for the command.
 
         """
         self.impl.drop_table(
 
         :param execution_options: Optional dictionary of
          execution options, will be passed to
-         :meth:`sqlalchemy.engine.base.Connection.execution_options`.
+         :meth:`sqlalchemy.engine.Connection.execution_options`.
         """
         self.migration_context.impl.execute(sql,
                     execution_options=execution_options)
         """Return the current 'bind'.
 
         Under normal circumstances, this is the
-        :class:`~sqlalchemy.engine.base.Connection` currently being used
+        :class:`~sqlalchemy.engine.Connection` currently being used
         to emit SQL to the database.
 
         In a SQL script context, this value is ``None``. [TODO: verify this]