535bc8e22e
A primary key is automatically unique, therefore if one or columns is
included in a primary key constraint there is no need to add a separate
unique constraint for these columns. Remove it.
Note that this only affects MySQL. Both SQLite and PostgreSQL appear to
ignore the duplicate unique constraint. As a result, it was necessary to
run auto-generation against MySQL instead of the default SQLite. The
actual command used was similar to what we normally do, however.
$ python keystone/common/sql/migrations/manage.py revision \
--autogenerate --message 'Remove duplicate constraints'
As always, the resulting schema migrations then needed some manual
tweaks to remove "please adjust!" comments and unnecessary imports but
they are correct.
Change-Id: I64252086f994901a5ebe05afec37a6afd3a192ee
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
|
||
|---|---|---|
| .. | ||
| versions | ||
| README.rst | ||
| __init__.py | ||
| autogen.py | ||
| env.py | ||
| manage.py | ||
| script.py.mako | ||
README.rst
Migrations for the database
This directory contains migrations for the database. These are implemented using alembic, a lightweight database migration tool designed for usage with SQLAlchemy.
The best place to start understanding Alembic is with its own tutorial.
You can also play around with the alembic command:
$ alembic --help