Roger, On Mon, Sep 8, 2014 at 12:26 AM, Roger Binns <rog...@rogerbinns.com> wrote: > On 07/09/14 19:11, Andres Riancho wrote: >> * I'm setting [4] "PRAGMA synchronous=OFF" for increased >> performance. Can this trigger malformed errors? > > Read the doc: > > https://sqlite.org/pragma.html#pragma_synchronous > > TLDR: yes > > To improve write performance use WAL: > > https://sqlite.org/wal.html > > Realise that SQLite can only be safe if at various points the data it wants > on the storage is actually completely written out and unaffected by power > failures etc. You can go a lot faster by not doing that, but then the data > isn't safe.
Well, I should have explained my use case a little bit more. In my project we use the database to store data during the process life, and then remove it when the process finishes. This will never be done by w3af: * Process #1: Store something in sqlite * Shutdown * Process #3: Read data from sqlite The flow always looks like: * Process #1: Store something in sqlite * Process #1: Read data from sqlite ... * Process #1: Store something in sqlite * Process #1: Read data from sqlite * Process #1; Close DB and remove file I got this into account when I decided to go with sync=OFF. For me if I have a power failure, it doesn't matter much, since "Process #1" will die, and there is no way for a new process of w3af to read the DB (broken or not). With this in mind, sync=OFF still looks like something that could cause "database malformed" errors? > Roger > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Andrés Riancho Project Leader at w3af - http://w3af.org/ Web Application Attack and Audit Framework Twitter: @w3af GPG: 0x93C344F3 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
