flipstone/orville

Drop index if exists

Closed this issue · 1 comments

Migrations that include DropIndex will fail if any of the columns that the index in question references have already been dropped. This is because when one drops a column in postgresql, postgres will also drop indexes and constraints on your behalf.

Consider amending DropIndex to perform a DROP INDEX IF EXISTS.

Thanks for the report. I think we should be able to get this in the stable branch relatively easily.