I agree. Just yesterday, I wrote a separate task that only did migrations for deploy.
Allen Madsen http://www.allenmadsen.com On Fri, Jan 31, 2014 at 1:13 PM, Emil S <[email protected]> wrote: > Currently the `db:migrate` rake task runs `dump` at the end which dumps > the database structure to `schema.rb` / `structure.sql`. This will be > useful in development environment but I can't see a reason why this should > run in production environment. Removing this step in production would make > deployments faster, I believe. Do others think that this should be fixed ? > > [Rails code that invokes `dump`]( > https://github.com/rails/rails/blob/8a5b480ebb46215210294b87a7ed9f1d8a032312/activerecord/lib/active_record/railties/databases.rake#L37) > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/rubyonrails-core. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/groups/opt_out.
