So, create another migration that would undo what the old problem one does... Would that be considered a better practice over just deleting the one you no longer need or is it just a personal preference?
Thanks On Mar 10, 5:02 pm, Rob Biedenharn <[email protected]> wrote: > On Mar 10, 2009, at 4:52 PM, Starr Horne wrote: > > >> 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? > > > Yeah, you can delete it. It's just a file. > > > -- > > Starr Horne > > My blog:http://starrhorne.com > > Check out my Helpdesk RailsKit:http://railskits.com/helpdesk/ > > Just create another migration that is the opposite of this one. > > -Rob > > Rob Biedenharn http://agileconsultingllc.com > [email protected] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
