On 12 Jul 2010, at 8:42pm, Noah Hart wrote: > consider that if you embed the WAL within the SQLite > database itself, past the high-water mark, it would also take case of this > problem.
No. Because whichever file stores the WAL information is stored in has to be opened with read/write permission. And some operating systems won't let you do that if the medium is read-only. (Some will -- arguably incorrectly.) One solution would be not to create a new WAL file until the first SQL command which requires a change (or the first command which isn't a SELECT). You should check for one when the database is opened, of course, just not create a new one. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
