Goutham Pacha Ravi f552549303 Fix wrong data type in database migration ... The `deleted` column in volume_type_extra_specs was as a boolean; The same column in share_type_extra_specs is an integer. However, the code migrating from volume_types to share_types assumes them to be vice-versa. This breaks downgrading from that migration. Further, the `id` column in share_type_extra_specs is a primary key field of Integer datatype. Such fields have auto-increment turned on by default; we shouldn't be copying the `id` from volume_type_extra_specs when we copy the data. Fix these bugs and add a unit test. Change-Id: Ic32a8a17b1b6a773de6dcf7792d9b37f6aed4a3c Needed-by: Ib0ad5fbfdf6297665c208149b08c8d21b3c232be Closes-Bug: 1643535		2016-12-01 05:44:58 +00:00
..
migrations	Fix wrong data type in database migration	2016-12-01 05:44:58 +00:00
sqlalchemy	Remove unused function in db api	2016-11-29 10:52:35 +01:00
__init__.py	Remove vim headers	2014-10-06 15:00:27 +02:00
api.py	Merge "Add provisioned_capacity_gb estimation"	2016-09-09 20:47:01 +00:00
base.py	Reuse 'periodic_task' from oslo_service	2015-07-20 19:38:19 +03:00
migration.py	Remove vim headers	2014-10-06 15:00:27 +02:00