golden hour

/opt/alt/python37/share/doc/alt-python37-alembic-0.8.3/docs/_sources/api

⬆️ Go Up

Upload

File/Folder	Size	Actions
autogenerate.txt	24.64 KB	Del OK
commands.txt	1.68 KB	Del OK
config.txt	1.2 KB	Del OK
ddl.txt	1.06 KB	Del OK
index.txt	1013 B	Del OK
operations.txt	6.61 KB	Del OK
overview.txt	3.33 KB	Del OK
runtime.txt	1.37 KB	Del OK
script.txt	450 B	Del OK

Edit: config.txt

.. _alembic.config.toplevel: ============== Configuration ============== .. note:: this section discusses the **internal API of Alembic** as regards internal configuration constructs. This section is only useful for developers who wish to extend the capabilities of Alembic. For documentation on configuration of an Alembic environment, please see :doc:`/tutorial`. The :class:`.Config` object represents the configuration passed to the Alembic environment. From an API usage perspective, it is needed for the following use cases: * to create a :class:`.ScriptDirectory`, which allows you to work with the actual script files in a migration environment * to create an :class:`.EnvironmentContext`, which allows you to actually run the ``env.py`` module within the migration environment * to programatically run any of the commands in the :ref:`alembic.command.toplevel` module. The :class:`.Config` is *not* needed for these cases: * to instantiate a :class:`.MigrationContext` directly - this object only needs a SQLAlchemy connection or dialect name. * to instantiate a :class:`.Operations` object - this object only needs a :class:`.MigrationContext`. .. automodule:: alembic.config :members:
Save