tabase (using file locking mechanism) and a parallel
> write-connection to be blocked until the locked is released. (No temporary
> files should be required until this moment.)
>
>
> - Original Message -
> From: Shawn Wagner
> To: SQLite mailing list
> Sent: S
s released. (No temporary
files should be required until this moment.)
- Original Message -
From: Shawn Wagner
To: SQLite mailing list
Sent: Sunday, March 24, 2019, 11:29:58
Subject: [sqlite] read-only database in WAL mode and temporary files
Even a read only database needs to create the wa
Even a read only database needs to create the wal journal if it doesn't
exist at the moment for a database that uses that mode:
https://www.sqlite.org/wal.html#read_only_databases
You might look into the immutable option mentioned there and see if it's
appropriate for your needs.
On Sun, Mar 24,
When I open a database in read-only mode (?mode=ro), I observe that the WAL and
SHM temporary files are created anyway. Is there any possibility to prevent the
creation of these files? Aren't they useless?
Even worse (using sqlite3.exe version 3.27.1):
.open test.db
pragma journal_mode=wal;
cre
4 matches
Mail list logo
