In that case then, rake db:migrate:all (or rake db:migrate:local) seems like a decent task name to run migrations on development+test only, no?
On 21 September 2010 11:48, Xavier Noria <[email protected]> wrote: > On Tue, Sep 21, 2010 at 5:20 PM, Ryan Bigg <[email protected]> > wrote: > > > This dual-migration should only happen if you're in the development > > environment. If you're in another environment such as staging it should > only > > run it for the current environment. > > But how can you tell from within the "test" environment? > > -- > 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]<rubyonrails-core%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. > > -- 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.
