change_column fails if index is already there about schema_plus HOT 9 CLOSED

oops sorry for the delay, managed to not see the notification for this. are you still experiencing this problem?

from schema_plus.

I am also seeing this issue.

from schema_plus.

if this is what i think it is (would need to see more detail from the log to know exactly what pg is complaining about), the workaround until it gets fixed is to precede the change_column with a remove_index, e.g.:

remove_index :mytable, :mycolumn
change_column :mytable, :mycolumn, ...

let me know if that does/doesn't work for you.

from schema_plus.

That did work for me, thanks! It even keeps/adds back the index I removed event though I don't specify the index again in my change_column.

from schema_plus.

glad that worked. and yes, i forgot to mention i'd expect that the index would come back: the bug is that change_column is auto-creating the index without first checking to see if it's already there.

from schema_plus.

Interestingly the remove_index was only needed on my up migration which was
only adding a :null => false. My down migration with :null => true works
just fine without removing the index first.

from schema_plus.

interesting... and a bit disturbing :) i'll keep it in mind when i get a chance to dig into this.

btw thanks for reporting the problem, and apologies for the inconvenience it caused you.

from schema_plus.

Also seeing this bug, and the fix you suggested worked fine. Our down migration required us do a remove_index before we did the change_column for null: true.

from schema_plus.

this should be fixed in master & next release.

from schema_plus.