Re: [sqlite] sqlite 3.22.0 read-only WAL mode clarifications

Hey Simon, thanks for your clarification. > Will any of the processes accessing the database have write permission > ? If not, if they're all just reading the existing database, then > there's no opportunity for corruption. Think of it as All of the processes (on "main" and remote host) have

[sqlite] sqlite 3.22.0 read-only WAL mode clarifications

sqlite 3.22.0 added the ability to read from WAL mode databases even if the application lacks write permission on the database and its containing directory, as long as the -shm and -wal files exist in that directory. Even though the wiki page states that WAL does not work over a network

Re: [sqlite] Crash in libsqlite3 with sqlite-3.21.0 and KDE plasmashell

Thanks for your prompt reply Richard. With this information I will go back to the KDE developers and let you know once/if there is further and detailed evidence for sqlites fault. Best regards Leonard Richard Hipp <d...@sqlite.org> writes: > On 1/19/18, Leonard Lausen <leon...@laus

[sqlite] Crash in libsqlite3 with sqlite-3.21.0 and KDE plasmashell

A crash in sqlite crashes plasmashell. Downstream bug https://bugs.kde.org/show_bug.cgi?id=388140. Please find the backtrace below: -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread