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	Use assert(Not)In/Greater(Equal)/LessEqual/IsNotNone	2016-09-30 09:43:49 +02:00
__init__.py	Files with no code must be left completely empty	2016-09-28 17:00:30 +07:00
fakes.py	Share Replication API and Scheduler Support	2016-02-11 19:45:37 +00:00
test_api.py	Fix db shim layer mismatches with implementation	2016-01-22 15:05:09 -05:00
test_migration.py	Fix typo in db migration test function name	2015-01-06 10:53:45 +01:00