On Tue, Feb 7, 2012 at 8:13 PM, David Barrett <dbarr...@expensify.com>wrote:
> On 02/07/2012 05:08 PM, Richard Hipp wrote: > >> There are no known limitations on the use of PRAGMA synchronous=OFF, WAL >> mode, and shared cache together. >> > > Ah, I guess that blows that theory. But thanks for the quick and thorough > response nonetheless. I'm a huge sqlite fan. I just wish I could figure > out this (non)malformed database issue! > > There have been no past bugs, that I recall, that might cause the problem you are seeing. Nevertheless, I'd be happy if you would upgrade from SQLite 3.7.2 to 3.7.10. I don't think that 3.7.10 will help this in any way, but we might get lucky. And in any event, if you are using 3.7.10, that means we don't have to go back as far in time in order to see the code you are using. My best guess still is that the command-line shell is somehow not seeing the shared-memory file that is created when the database is running in WAL mode. Or, perhaps the posix advisory locks are not working on that shared-memory file. The shared-memory file is the one with the "-shm" suffix. Of course, the command-line tool and the server process must both be running on the same machine or else they won't be able to see each others shared memory, and stuff like this will happen. You are running both processes on the same machine, right? > > -david > Founder and CEO of Expensify > Follow us at http://twitter.com/expensify > ______________________________**_________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users<http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users> > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
