anotherim/anotherim-desktop
2
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

service/database: use WAL mode + safe PRAGMA synchronous setting

Browse source 
Setting PRAGMA synchronous = 0 is really unsafe, and leads to database
corruption (which I've personally experienced). This commit uses
SQLite's Write-Ahead Log (WAL) [1] instead, together with synchronous =
NORMAL. According to [1], this trades off performance for durability
(i.e. it's possible that some transactions may not have committed if the
power gets lost), but still guarantees that the database won't corrupt
itself.

Together, these changes should improve reliability whilst either
improving or having no effect on performance.

[1]: https://www.sqlite.org/wal.html
This commit is contained in:
eta 2020-10-04 13:54:11 +01:00 committed by Marvin W
parent 7b58c1596a
commit 9cc3382abe
1 changed files with 3 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
libdino/src/service/database.vala
View file

@ -293,12 +293,9 @@ public class Database : Qlite.Database {
mam_catchup = new MamCatchupTable(this); mam_catchup = new MamCatchupTable(this);
settings = new SettingsTable(this); settings = new SettingsTable(this);
init({ account, jid, entity, content_item, message, message_correction, real_jid, file_transfer, conversation, avatar, entity_identity, entity_feature, roster, mam_catchup, settings }); init({ account, jid, entity, content_item, message, message_correction, real_jid, file_transfer, conversation, avatar, entity_identity, entity_feature, roster, mam_catchup, settings });
try { exec("PRAGMA journal_mode = WAL");
exec("PRAGMA synchronous=0"); exec("PRAGMA synchronous = NORMAL");
} catch (Error e) { } exec("PRAGMA secure_delete = ON");
try {
exec("PRAGMA secure_delete=1");
} catch (Error e) { }
} }
public override void migrate(long oldVersion) { public override void migrate(long oldVersion) {