On Mon, Sep 8, 2014 at 2:27 PM, Roger Binns <rog...@rogerbinns.com> wrote: > On 08/09/14 03:29, Andres Riancho wrote: >> In my project we use the database to store data during the process >> life, and then remove it when the process finishes. > > It sounds like what you could use temporary tables and let SQLite do the > work for you.
Was completely unaware of that feature, will take a look. >> With this in mind, sync=OFF still looks like something that could >> cause "database malformed" errors? > > The problem with synchronous off is that all your code has to be perfect, My code IS perfect (??) > not to mention the operating system and hardware. While you might be > reasonably convinced right now that interactions between all the parts of > code and database are safe, all it takes is some changes in the future to > invalidate that. > > I strongly recommend not playing with fire. Ok, makes sense. Merging Simon's answer: > Hmmm. How about this. Stop turning synchronous off for a month or two and > see if people stop reporting the fault. Yep, that's a great idea. > 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
