On Friday, 28 June, 2019 07:37, Thomas Kurz wrote:
>> A WAL file left behind is a sign of a problem in the app which
>should be corrected.
>I have exactly this problem and don't like the SHM and WAL files
>being left behind. I have even tried "pragma wal_checkpoint(full)"
>before closing the
Haha :) Thanks for the insight. Hadn't looked at it that way.
Ingo
On 28-6-2019 11:52, Warren Young wrote:
> You’ve basically got it backwards.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
> A WAL file left behind is a sign of a problem in the app which should be
> corrected.
I have exactly this problem and don't like the SHM and WAL files being left
behind. I have even tried "pragma wal_checkpoint(full)" before closing the
connection, but there are still situations where the
On Jun 28, 2019, at 2:12 AM, ingo wrote:
>
> I see a wal file being created and deleted. Just for my
> understanding, would it be of advantage to have a second persistent
> connection just for keeping the wal alive?
You’ve basically got it backwards.
It’s a *good thing* when the WAL file
Hi,
THe most persists after it has been set.
The file comes and goes as needed. I seem to remember there are some
caveats in the manual about what directory permissions are required and
what happens when you can write the journal file and the database file
but not the directory that contains
From the docs,
"The WAL journaling mode uses a write-ahead log instead of a rollback
journal to implement transactions. The WAL journaling mode is
persistent; after being set it stays in effect across multiple database
connections and after closing and reopening the database."
When using 'single
6 matches
Mail list logo
