"Luke Evans" <luk...@me.com> schrieb im Newsbeitrag news:3be16206-d0c6-4041-a3a6-ca3c069ee...@me.com...
> It's Objective-C, but all the SQLite interfacing bits are pure C > directly driving the SQLite API compiled into the program > (3.6.22 amalgamation). Just to make sure ... do you really create different DB-Handles (over dedicated DBOpen-Calls) in each of your threads? Aside from that, could you recompile the SQLite-library on your system explicitely with: SQLITE_THREADSAFE=2 and SQLITE_OMIT_SHARED_CACHE And then just open the DBHandles without giving explicit "sqlite_open_v2() Flags"? Maybe (if that solves these "serialized Read-access-issues") it could indicate, that the "dynamic access-mode-switches" in sqlite_open_v2() do not work as expected in threaded mode (at least on your system-OS). Olaf _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
