I have a migration "x" that when it runs self.up it adds a new column to a table, and of course when self. down is run it deletes said table...
After I ran this migration I continued to work and in the process added a couple other migrations. After a while I realized that the column migration "x" created was a mistake and I no longer need it. So I ran rake db:migrate:down VERSION=x to delete the column. It worked great, but the problem is whenever I added another migration than ran rake db:migrate, migration "x" ran its self.up again and the column I no longer wanted was built back into my schema. What the best way to handle something like this? Is it insane to just manually delete a migration file to prevent it from ever being ran again? Thanks heaps, Elliott --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
