| Server IP : 78.140.185.180 / Your IP : 216.73.216.28 Web Server : LiteSpeed System : Linux cpanel13.v.fozzy.com 4.18.0-513.11.1.lve.el8.x86_64 #1 SMP Thu Jan 18 16:21:02 UTC 2024 x86_64 User : builderbox ( 1072) PHP Version : 7.3.33 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : OFF | Pkexec : OFF Directory : /proc/thread-self/root/opt/alt/python37/share/doc/alt-python37-alembic/docs/build/api/ |
Upload File : |
.. _alembic.runtime.environment.toplevel:
=======================
Runtime Objects
=======================
The "runtime" of Alembic involves the :class:`.EnvironmentContext`
and :class:`.MigrationContext` objects. These are the objects that are
in play once the ``env.py`` script is loaded up by a command and
a migration operation proceeds.
The Environment Context
=======================
The :class:`.EnvironmentContext` class provides most of the
API used within an ``env.py`` script. Within ``env.py``,
the instantated :class:`.EnvironmentContext` is made available
via a special *proxy module* called ``alembic.context``. That is,
you can import ``alembic.context`` like a regular Python module,
and each name you call upon it is ultimately routed towards the
current :class:`.EnvironmentContext` in use.
In particular, the key method used within ``env.py`` is :meth:`.EnvironmentContext.configure`,
which establishes all the details about how the database will be accessed.
.. automodule:: alembic.runtime.environment
:members: EnvironmentContext
.. _alembic.runtime.migration.toplevel:
The Migration Context
=====================
The :class:`.MigrationContext` handles the actual work to be performed
against a database backend as migration operations proceed. It is generally
not exposed to the end-user.
.. automodule:: alembic.runtime.migration
:members: MigrationContext