Use SQLAlchemy to drop foreign key in DB migrate
A foreign key constraint needs to be removed in order to succeed in the DB migration. An earlier submitted fix for this uses a mysql drop statement. I think it's cleaner to use sqlalchemy to do this, as it's done this way in other version migrations as well. Fix for bug 907254. Update: IBM from 1928 called, they want their 80 CPL limit back. - on a more serious note, fixed jenkins PEP8 failure Update2: Replaced tab by a spaces Update3: Don't do Foreign Key stuff if the engine is sqlite Update4: Add myself to the Authors file Update5: With the correct mail address Change-Id: Ib021e0ddb2c80ee63888435a9e3761c053534160
This commit is contained in:
1
Authors
1
Authors
@@ -30,6 +30,7 @@ Chris Behrens <cbehrens@codestud.com>
|
||||
Christian Berendt <berendt@b1-systems.de>
|
||||
Christopher MacGown <chris@pistoncloud.com>
|
||||
Chuck Short <zulcss@ubuntu.com>
|
||||
Cor Cornelisse <cor@hyves.nl>
|
||||
Cory Wright <corywright@gmail.com>
|
||||
Dan Prince <dan.prince@rackspace.com>
|
||||
Dan Wendlandt <dan@nicira.com>
|
||||
|
||||
Reference in New Issue
Block a user