No, I needed to set a timeout (see previous messages in this thread). I've fixed my problem. I'm suggesting now that the documentation for SQLITE_BUSY is incomplete.
Jeff > On Aug 22, 2015, at 5:13 AM, Eduardo Morras <emorrasg at yahoo.es> wrote: > > On Sat, 22 Aug 2015 05:07:55 -0500 > Jeff M <jmat at mac.com> wrote: > >> The doc page for SQLITE_BUSY covers SQLITE_BUSY when there are >> multiple connections to the database. >> >> SQLite Result Codes (SQLITE_BUSY) >> http://www.sqlite.org/rescode.html#busy >> >> But, I have only one connection. I believe the case where >> SQLITE_BUSY is returned by sqlite_close() due to unfinalized prepared >> statements should be mentioned there. > > Perhaps you forget to call sqlite3_finalize() on at least one query of your > code. > >> Jeff > > > --- --- > Eduardo Morras <emorrasg at yahoo.es> >
