Thanks for the help. But then what is the purpose of db:migrate:down (and self.down method in migration file)? The method self.down does roll back any changes if needed, but its effects are not reflected in other areas such as 'rake test'.
I am probably going to do 'rake db:migrate:down' and then 'svn remove' for the particular migration file. Thanks, Shantanu. James Mitchell wrote: > I see. Ok, I see a couple of options here. Some of which have been > suggested already. > > 1. Rip out (svn remove) the migrations you don't want. Reset the db. > 2. Add new migrations to add/fix/remove the changes. > 3. db:migrate down to the lowest possible version, comment out the the > guts of the migrations you don't want. Then migrate back up. > 4. Something entirely different that I can't think of right now:) > > > Which approach you should take depends on a couple of factors ... such > as ... whether the app is in production yet, how much code and tests > are affected, how true to the "rails way" you want to stay ... things > like that. > > Good luck with it. > > > On 12/3/08, Shantanu Pavgi <[EMAIL PROTECTED]> wrote: >> migrations. >> >>> Are your trying to run a prior version of your app? If so, you should >>>> >> > >> > > > -- > > -- > James Mitchell -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
