On Nov 30, 2007 1:35 PM, DHH <[EMAIL PROTECTED]> wrote: > I don't think I understand this. Why do you want or need to continuously test > the migrations?
Let me try to explain. * there is no up-to-date development environment on the continuous integration box * but I do want to rebuild the database from scratch in every CI build. From what? * if I use db/schema.rb, I am relying on an artefact that was automatically generated in somebody's development environment. Which is not how it will be done in production. I also cannot expect everybody to always pay attention when checking-in auto-generated artefacts. * running all migrations then looks like a better choice. > Once everyone has been moved, the migrations are useless and could > essentially be deleted. Yeah, having many migrations floating around is awkward, too. One can take schema dumper output and make a new baseline migration out of it, with the same number as the DB_VERSION in the last prod release. -- 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 -~----------~----~----~----~------~----~------~--~---
