On Mon, Jun 23, 2014 at 3:31 PM, Simon Slavin <[email protected]> wrote:
> > On 23 Jun 2014, at 11:17am, João Ramos <[email protected]> wrote: > > > On Mon, Jun 23, 2014 at 10:58 AM, Simon Slavin <[email protected]> > wrote: > > > >> Are you finalizing all these SQL commands (or using _exec() which > amounts > >> to the same thing) ? > > > > Yes, I double checked and everything is being terminated properly (e.g.: > > sqlite3_reset, etc.) and without any error codes. > > Excellent. > > >> What do you mean by 'releases' here ? If you have other threads using > the > >> same connection, you're obviously not closing it. > > > > No, the SQLite connection isn't closed. By "release" I mean release back > to > > the thread pool. > > Okay. I would temporarily, for testing purposes, turn off shared cache > mode. Another thing to try messing with is read_uncommitted: > Turning off shared cache mode solved this (read uncommitted has always been off). > > <http://www.sqlite.org/pragma.html#pragma_read_uncommitted> > > Which of these does or doesn't change how your app behaves might help you > diagnose the problem. > > Simon. > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
