Well finally found the problem: a forgotten sqlite3_finalize() call. Very disturbing, I'd expect leakage, not the results I was seeing.
Normand -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Normand Mongeau Sent: October-30-13 9:51 AM To: 'General Discussion of SQLite Database' Subject: Re: [sqlite] Problem with SQLITE_BUSY Using the straight C API of SQLite. -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Simon Slavin Sent: October-30-13 9:39 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Problem with SQLITE_BUSY On 30 Oct 2013, at 1:00pm, Normand Mongeau <nmong...@theobjects.com> wrote: > Could this be related to this: in A, the database connection is > created in the main program, but is passed down to a dll that loads > another dll that uses the connection to do the writes. Maybe the dll > should open its own connection? Are you addressing SQLite though its own C API, or are you using a library which says it does SQLite things for you ? If you're using a library, which 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 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
