Scott Hess wrote: > WRT #3, you could also consider journal_mode off (or memory, if your code > requires transactions to work right). In that case, the database state is > indeterminate if you have an app-level crash, but you should be fine if you > make it to the end.
It would be a better idea to change to the rollback journal mode (DELETE/ TRUNCATE/PERSIST) - it's guaranteed to work correctly in all situations, and with a small database to be filled, the journal cannot become large because it stores only _old_ data. Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
