Dropping ForeignKeyConstraints does not work with sqlite
Bug #1423955 reported by
Matt Riedemann
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| sqlalchemy-migrate |
Fix Committed
|
High
|
Matt Riedemann | ||
Bug Description
This is blocking a change in a nova migration:
Because of the 273 migration which added FKeys for sqlite but didn't add the downgrade option b/c of lack of support in sqlalchemy-migrate:
https:/
The alternative is adding .sql scripts for sqlite in other projects to basically create a temp table with the new schema, migrate data to the new table, then drop the old table and rename the temp table, e.g.:
https:/
That's what sqlalchemy-migrate essentially does for dropping UniqueConstraints with sqlite here:
https:/
We can probably do something similar for FKeys and sqlite.
| Changed in sqlalchemy-migrate: | |
| importance: | Undecided → High |
| status: | New → Triaged |
Revision history for this message
| Johannes Erdfelt (johannes.erdfelt) wrote | #1 |
Revision history for this message
| Matt Riedemann (mriedem) wrote | #2 |
| Changed in sqlalchemy-migrate: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Matt Riedemann (mriedem) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to sqlalchemy-migrate (master) | #3 |
| Changed in sqlalchemy-migrate: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
To be fair, the 273 migration isn't causing any problems, it just took the easy way out :)