Gary Doades wrote: > Jian Lin wrote: >> in RAM as much as possible? > The database can be cached in ram by most database engines. However, > most database engines will also make sure that every transaction > (insert, update, delete) is committed to disk by forcing a write to the > physical disk for *every* transaction. If the database engine doesn't do > this you risk losing part or all of your database if some kind of > failure happens part way though your updates. > > If you don't care if you lose part or all of your database, most > database engines also have a setting for this.....
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? -- 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 -~----------~----~----~----~------~----~------~--~---
