I had a crazy idea today based off a reader's question[1]. Why are rake db:migrate and rake db:test:prepare two different tasks? Why can't we have rake db:migrate migrate both the development and the test database at the same time? So many noobs (I'll include myself in that basket too) get tripped up on this. How many times have you ran into it?
>From what I can see, there is no reason at all why the development and test databases should be different. What would you think about having these as one task in Rails 3.0.1 or Rails 3.1, with obviously a deprecation warning for rake db:test:prepare or something? [1] http://www.manning-sandbox.com/thread.jspa?threadID=39618&tstart=0 -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en.
