On 01/24/2013 03:25 AM, Teg wrote:
I use "insert or replace" heavily. In debug mode, I set it to use temp file on disk so, I can watch the disk IO, in release mode I set it to temp file in memory. The danger is that if you ever do anything that requires a bunch of temp file, you can easily run out of RAM. Adding and deleting indexes for example while temp store is set to memory will run you out of address space on a larger DB and a 32 bit system (windows).
VACUUM can also create large temporary files (since it uses a temp file to construct the new database image before copying it over the top of the old). Other commands (other than CREATE INDEX and VACUUM) *usually* don't use too much temp space. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
