manila/manila/db/migrations
Valeriy Ponomaryov 7ba41320f3 Fix 'project_share_type_quotas' DB table unique constraint
It should be possible to use share type quotas in each project/tenant.
But we get error trying to set share types quota in second+ project
for the same share type. It happens so due to the bug in DB schema,
where we don't have 'project_id' in unique constraint.
So, add new DB migration that fixes unique constraint and cover it with
DB and tempest tests.

Change-Id: I1405ced4e12b40904b7227c9f6285e2775005f8a
Closes-Bug: #1722707
2017-10-14 23:22:10 +03:00
..
alembic Fix 'project_share_type_quotas' DB table unique constraint 2017-10-14 23:22:10 +03:00
__init__.py Use Alembic instead of Sqlalchemy-migrate in Manila 2014-08-26 17:12:57 +04:00
alembic.ini Use Alembic instead of Sqlalchemy-migrate in Manila 2014-08-26 17:12:57 +04:00
utils.py Remove models usage from migrations 2015-07-13 11:58:15 +03:00