Jian Lin wrote: > so i re-ran the test and it worked quite quickly... down to 1 minute or > so instead of 30 minutes... (for several pages)... and the db size is > only 2.5MB (i created another rails project to start anew). So > if we are just write scripts, and running with script/runner test.rb, > how can we turn the "force write" feature of the sqlite3 off?
Are you running inside a transaction? sqlite3 in transaction mode is super-fast... (Jumping into the thread late, why should a test push 6 000 records? Such a test is not exactly a "unit" test, and alternate strategies should work better.) -- Phlip http://flea.sourceforge.net/resume.html --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
