diff options
author | Roman Podoliaka <rpodolyaka@mirantis.com> | 2014-05-13 12:45:48 +0300 |
---|---|---|
committer | Ilya Pekelny <ipekelny@mirantis.com> | 2014-07-08 11:14:00 +0300 |
commit | 404de362a3cf8fb88e827fe0b4bf6b2d5baea405 (patch) | |
tree | a3263eef91f2027d7b832cb1cbbcbf65d10d1356 /setup.cfg | |
parent | f4074f7086033fb2cc7a76337851ee4043eb0913 (diff) | |
download | oslo-db-0.3.0.tar.gz |
Add a base test case for DB schema comparison0.3.0
Add a base test case that allows to check if the DB schema obtained
by applying of migration scripts is equal to the one produced from
models definitions. It's very important that those two stay in sync
to be able to use models definitions for generation of the initial
DB schema. Though, due to the using of sqlalchemy-migrate (since we
had to write migration scripts manually and alembic can generate
them automatically) we have many divergences in projects right now,
which must be detected and fixed.
Fortunately, we can now rely on alembic + sqlalchemy implementation
of schema comparison instead of writing our own tools.
Blueprint: sync-models-with-migrations
Change-Id: I2d2c35987426dacb1f566569d23a80eee3575a58
Diffstat (limited to 'setup.cfg')
0 files changed, 0 insertions, 0 deletions