Actually, I am not using sqlite at the API level. That's why prepared a bunch of batch files that reproduce the issue with sqlite command line shell. To answer your question, the queries complete in sqlite3 command line, and they also complete successfully using the API, albeit, through a wrapper that I am using.
Regards, Dan On Sun, Sep 9, 2012 at 9:31 PM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 9 Sep 2012, at 9:15pm, Daniel Frimerman <danielfrimer...@gmail.com> > wrote: > > > The reason I think there has to be 50 rows is because on FULL mode for > > example, the I/O buffers are flushed, and it's consistently missing 1 > > record as opposed to any other number of records. I insert 50 records, > the > > sqlite3 command line utility executes the script, and I get to a stage > > where I can write commands to the console. What I mean is that as far as > > sqlite is concerned, it has written the data to disk and also instructed > > the OS to flush the buffers. > > Are you checking the result codes returned by every SQLite call you > execute ? I'm not talking about the one that is causing the error but > every one in your app before it executes that one. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
