elliottg wrote:
> 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
I'm just editing migration file to add/remove columns and don't create
new migrations to the same table until first branch/release version...
then add new migration file (for the same table, if needed) and continue
to add/remove columns until next branch/release version commit.
It's silly to add migration file for each column change within one
version...
tom
--
===============================================================================
Tomas Meinlschmidt, MS {MCT, MCP+I, MCSE, AER}, NetApp Filer/NetCache
www.meinlschmidt.com www.maxwellrender.cz www.lightgems.cz
===============================================================================
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
