On 11 Apr 2017, at 12:33am, Simon Slavin <slav...@bigfraud.org> wrote:
> It may be that the documentation should be updated to reflect this. After another look I’m going to withdraw everything I wrote in the thread. <https://sqlite.org/wal.html> in section 1 says: "It is not possible to open read-only WAL databases. The opening process must have write privileges for "-shm" wal-index shared memory file associated with the database, if that file exists, or else write access on the directory containing the database file if the "-shm" file does not exist." J. King posted that earlier in the thread, but I didn’t see it before I replied. I think it’s clear enough. It’s the permissions granted by the OS that’s important, not the mode you tell SQLite to open the file in. However, I went back and read your original post and you weren’t asking what I thought you were asking. You may have found something strange going on. My only doubt is whether the individual files (database and -shm file) were marked read-only. If not, then there seems to be something wrong somewhere. Sorry I wasted time upthread. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
