On Nov 30, 2007 8:46 AM, DHH <[EMAIL PROTECTED]> wrote: > In that context, it doesn't make sense to use migrations for the test > database because the test database does not have permanent data of > importance.
I think, it does make sense to run migrations in the continuous integration loop (but not in the local build). Reason: you want to test them, but you don't want to slow down the local build. A fairly common practice is to use 001_initial_schema migration as the only migration on the project for as long as there is no valuable production data to preserve. > But it seems that this misuse of migrations highlights something that might > be lacking: a data seeding system. Yup. Another common practice is db/dataload.rb, a script of ActiveRecord operations to put some data into the database, with the corresponding db:dataload Rake task. Using AR and domain to create this data is much easier than doing the same thing with YAML-based fixtures. -- Alexey Verkhovsky CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] RubyWorks [http://rubyworks.thoughtworks.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 -~----------~----~----~----~------~----~------~--~---
