Tom Spencer wrote: > I did actually think of chmodding the file with every connection.
The sqlite3_open_v2 call does let you specify SQLITE_OPEN_READONLY. If your wrapper doesn't provide this then the simplest thing would be to update the wrapper. http://www.sqlite.org/c3ref/open.html Altering the file permissions is a bad idea unless the database is never going to be modified again. This is because a crash at an inopportune moment may require using the journal to fix the database, even when opening read only. Roger _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
