On 12/20/07, Xavier Noria <[EMAIL PROTECTED]> wrote: > > The task db:reset runs db:schema:load instead of db:migrate. Written > that way, any people using FKs or initializing data in migrations have > to switch to the brand new db:migrate:reset. That smells like > premature optimization, which is the rationale? Wouldn't be easier to > let db:reset run migrations?
This has been discussed quite a bit on this list already, please check out the archives for the back-story. In the mean time please use rake db:migrate:reset (included in 2.0.2) to get the functionality that you'd like. -- Josh Knowles phone: 509-979-1593 email: [EMAIL PROTECTED] web: http://joshknowles.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
