Yea, I've done this too. Basically in my chained :clone_structure I copy the schema migrations to the test database and have the same task along with :dump noop unless the migrations are out of sync. This way I get to avoid a costly clone which takes almost 2 minutes for my legacy database.
- Ken On Sep 24, 2010, at 12:45 AM, George wrote: > > This is a nice ideal. However I agree with others who say that when > the schema gets large, recreating it can be slow. And slow tests are a > nightmare. > > What if we could skip db:test:prepare if a NOPREP environment variable > is given? Or had an extra set of tasks, say test:quick:unit etc, which > skipped it? I've personally taken to doing the former in a large > project. -- 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.
