> I see this issue is distilling into three separate arguments for > migration-based test DB setup: > > 1. migrations (in their entirety) need testing too
I think the fact that I immediately disagree with this is a sign that we're facing two distinct problems which require two distinct solutions. If you're building a single application with a single database installation, you will *never* need to run your migrations from start to finish. Basecamp is up and running, no-one's out there downloading it and setting up a new installation. The old migrations are simply interesting relics of previous schema versions. Of no interest to anyone. By contrast if you're constantly installing new versions of your application all over the place (say, mephisto) then your needs are completely different. > 2. migrations are the most capable means of building a database > (including test). > 3. Rails is sending an inconsistent message: migrations for > development and production, but schema dumper for test. > > What's the argument for the schema dumper? > > This thread is probably reaching the end of it's useful like, but I > would like to close with a request: please consider endorsing (test, > +1) ticket 8389 or something similar. I think that we're well past the point of getting some ROI on this thread, and it's definitely not something that's going to change in the short term. Let's get a plugin out of 8389 and see how people like using it. We can re-evaluate the pros and cons when it comes time to do 2.1. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
