I've got WAL databases that I'm trying to do analysis on and DON'T want them
modified. I can PRAGMA wal_autocheckpoint=0; to disable auto-checkpoint'ing but
when I exit the shell I see auto-checkpoint'ing is done -- foo.db-wal and
foo.db-shm are gone and foo.db is modified. That's bad. I can't mark the files
readonly various shell operations report disk I/O error.
I'm not even sure if PRAGMA wal_autocheckpoint=0 is enough as the sequence
PRAGMA wal_autocheckpoint=0;
.q
shows files untouched but
PRAGMA wal_autocheckpoint=0;
PRAGMA user_version;
.q
checkpointed the database.
Is it possible to use the CLI to read a WAL database and exit without modifying
the database? I can write my own custom code to do it if disable autocheckpoint
(and set SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE?) but it'd be handy to be able to use
the CLI. I'm effectively looking for a -readonly option, or how to achieve that
net effect
Is this possible today? If not, what needs to change to support this behavior?
* Howard
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
