How to keep journal mode WAL? about sqlitebrowser HOT 9 CLOSED

I think this is a SQLite thing. We have no code regarding these files, it all happens in SQLite. On https://www.sqlite.org/wal.html it says that "the wal-index backing file is deleted when the last database connection disconnects" which is exactly what happens on my system: If I have multiple instances of our application with the same file opened, I can close any of them and the files stay where they are. If I close the last one though, they are deleted.

from sqlitebrowser.

Oh I see. I do notice that when I open the sqlite file again those shm and wal files reappear. Thanks for your answer!

from sqlitebrowser.

Thanks for the feedback. Glad I could help 😃

from sqlitebrowser.

Stupid question, but is there a way to open WAL files directly? I have a .db-wal file I was looking to browse apart from my .db.

Thanks!

from sqlitebrowser.

.db-wal is a temporary file created by the sqlite3 code/library, you cannot directly open such file.
There should be a corresponding sqlite3 db file.

from sqlitebrowser.

Thanks so much for the help, Peinthor! Indeed there is, would this main db reflect the data in the Write-Ahead log before the commit to purge it? If not, is there any way at all to see what this data is before it has been added to the main db?

from sqlitebrowser.

well, kinda. I don't know the implementation details, but I think this WAL file has checkpoints and uncommitted data.
But for details you should read the sqlite3 documentation:
https://www.sqlite.org/wal.html

from sqlitebrowser.

@sammarcus wrote 'stupid question'. With the sole exception of the unasked there is no such thing as a 'stupid question'. Stupid answers however there are unfortunately too many...

Back on-topic: like someone said: by opening more than one session (e.g. more TerminalTabs) one can easily have more WA-L and/or SHM-files and investigate them with any tool/language (Perl is an easy example) capable of handling binary files. With the help of SQLite's doc you're able to analyze them and search for nugs and other reasons of corrupted databases.

"In bocca al lupo",
Klaas

from sqlitebrowser.

@rp- thanks so much for that documentation! I had seen it before but gave it another reread, made some new discoveries. appreciate the link!

@Z4us thank you as well!! I'm just starting out so I always like to preface my beginner questions with that disclaimer but the git community has been so friendly. I got it all figured out.. thanks again!

from sqlitebrowser.