openstack/deb-python-oslo.db
Code Issues Proposed changes
9b79858453
deb-python-oslo.db/oslo_db/sqlalchemy/migration_cli
History
Victor Sergeyev 3fb50986fa Refactor database migration manager to use given engine 
Removing global engine object introduces some changes
to migration api.
Basically we need to move engine creation to outer scope.
In order to address these issues we need to refactor alembic api.

Co-Authored-By: Dmitry Shulyak <dshulyak@mirantis.com>

Adopted from Ia2f9586c4e9c31339dd7dcd9f45a58e8a8409921

Change-Id: Ic7dcf1d2f38388bd1e5a517ce60190bff499686a
2015-01-27 19:12:16 +00:00
..
__init__.py Move files out of the namespace package 2014-12-24 13:28:48 +02:00
ext_alembic.py Refactor database migration manager to use given engine 2015-01-27 19:12:16 +00:00
ext_base.py Move files out of the namespace package 2014-12-24 13:28:48 +02:00
ext_migrate.py Refactor database migration manager to use given engine 2015-01-27 19:12:16 +00:00
manager.py Refactor database migration manager to use given engine 2015-01-27 19:12:16 +00:00
README.rst Move files out of the namespace package 2014-12-24 13:28:48 +02:00

README.rst

This module could be used either for: 1. Smooth transition from migrate tool to alembic 2. As standalone alembic tool

Core points: 1. Upgrade/downgrade database with usage of alembic/migrate migrations or both 2. Compatibility with oslo.config 3. The way to autogenerate new revisions or stamps