> I find especially the *-wal access attempt pretty strange as we do not have > WAL enabled for our database: it is set to the default journal mode (DELETE). > Is this normal behaviour? Or is this influenced by some setting I don't know > of?
I think when SQLite opens the database it can't trust its contents right away, so it can't know yet that it's in DELETE journal mode. SQLite must check for presence of both files *-wal and *-journal. If none of them exist (failed QueryOpen) then database should be in complete and trusted state, so SQLite can read its contents and see what journal mode is in it. That's what you see and it can't be changed. Pavel On Mon, Feb 21, 2011 at 9:15 AM, Gert Corthout <gert_corth...@hotmail.com> wrote: > > > > > hello, > > we recently switched from SQLite version 3.5.4 to 3.7.5. When I run process > monitor on our machines I see a lot of failed file access attempts that > weren't there before (v 3.5.4). > It is failed QueryOpen (NAME NOT FOUND) events for DBASE-NAME.db3-wal and > DBASE-NAME.db3-journal. > > I find especially the *-wal access attempt pretty strange as we do not have > WAL enabled for our database: it is set to the default journal mode (DELETE). > Is this normal behaviour? Or is this influenced by some setting I don't know > of? > > kind regards, > Gert > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
