The answer gets a bit more strict if there are multiple developers involved. In that case, I'd always create the extra migration.
However, if you never checked the migration into source control, then migrate:down, change it and migrate:up (or just delete it), is the right thing to do even in a multi-user development environment. -Rob On Mar 10, 2009, at 5:37 PM, elliottg wrote: > > Thanks for the insight. > > EG > > On Mar 10, 5:31 pm, Starr Horne <[email protected]> wrote: >>> 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? >> >> If you're in production, or far along in development it's probably >> best to create the extra migration. >> >> If you're early in development, I'd just delete it to keep things >> clean. >> >> SH >> >> -- >> Starr Horne >> My blog:http://starrhorne.com >> Check out my Helpdesk RailsKit:http://railskits.com/helpdesk/ > > Rob Biedenharn http://agileconsultingllc.com [email protected] +1 513-295-4739 Skype: rob.biedenharn --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
