postgresql downgrade fails in migration 018 and 002 due to foreign keys
Bug #1266595 reported by
Jay Bryant
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Ivan Kolodyazhny |
Bug Description
Similar to the problem reported in bug 1265944 for mysql, downgrades for postgresql also fail due to an attempt to drop tables that still have foreign keys defined.
The solution implemented for mysql does not work for postgresql. For postgresql we need to drop the table in question using the 'CASCADE' option.
Changed in cinder: | |
status: | New → Confirmed |
Changed in cinder: | |
assignee: | nobody → Ivan Kolodyazhny (e0ne) |
Changed in cinder: | |
status: | Confirmed → In Progress |
Changed in cinder: | |
milestone: | none → kilo-2 |
Changed in cinder: | |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | kilo-2 → 2015.1.0 |
To post a comment you must log in.
Thanks for taking this Ivan. Had forgotten about it/not had time to look at it further.