Because maybe you don't want it to happen all at once, maybe you need to stage things. Imagine you're developing new features for an existing system, and you create some destructive migrations. You want those to automatically affect your other environments when you might not even be done writing and testing code?
A better idea is to realize that these processes are separate and manual and get in the habit of doing it yourself. Plus, if you just use "rake" instead of running a specific test, rake will warn you that you have pending migrations. On Feb 2, 5:47 pm, Fernando Perez <rails-mailing-l...@andreas-s.net> wrote: > Or at least development and test. How many times did I find myself > banging my head on the table with buggy tests until I figured out that I > had forgotten to migrate the test database. > > Why rake db:migrate doesn't by default migrate all environments at the > same time? > -- > Posted viahttp://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 rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
