Rob Biedenharn wrote: [...] > I think I recall this kind of question being answered before. The > gist was that you can define a 'facts' section of your database.yml > (similar to your 'development' or 'test' section) and create the > connection to the special 'facts' database for that model. It would > be unaffected by the initialization of the 'test' database.
What, create a second database for that data? Why? More overhead, more difference from production, more general hassle. I still maintain that the right answer is not to test with all 85,000 records. Just create what you need for a particular test. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en.
