Quoth Roger Binns <rog...@rogerbinns.com>, on 2011-06-01 00:21:44 -0700: > On 05/31/2011 12:18 PM, Jan Hudec wrote: > > - Is there any way to speed it up? > > Another way (somewhat hinted at by Nico) is that you can create these tables > in separate databases and use attach to bring them in. To drop a table you > can just detach and then delete the database file (at a later point if > necessary). If the new database is going to be the approximately the same > size as the old one then you can overwrite the database header to cause the > database to be empty but already the allocated size so the operating system > won't have to go through a free then allocate cycle for the file blocks.
This is a reasonable suggestion, but watch out for the limit on the number of attached databases. You cannot reliably have more than 30 of them on a custom compiled SQLite3 (for 32-bit integers; the doc is silent re int64 type) and the default is a compile-time limit of 10. Whether this is a problem depends on your data and application architecture. ---> Drake Wilson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
