On 30 Oct 2013, at 4:03pm, Normand Mongeau <nmong...@theobjects.com> wrote:
> Well finally found the problem: a forgotten sqlite3_finalize() call. > > Very disturbing, I'd expect leakage, not the results I was seeing. SQLite has to keep the state of your SELECT available until you tell it you're done with that SELECT. After all, you might look at the results you have retrieved and decide to make some changes based on what you see there. This means SQLite has to stop everything from changing the database. Therefore it locks it. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
