Re: [KDE-pim] New Install: AKONADI wit PostgreSQL
Martin Steigerwald <[email protected]>
| Newsgroups | gmane.comp.kde.users.pim |
|---|---|
| Message-ID | <5423861.DvuYhMxLoT@merkaba> |
Erik Quaeghebeur - 01.01.21, 16:43:01 CET: > On donderdag 31 december 2020 12:39:51 CET, Martin Steigerwald wrote: > > I think it is too much to ask from the user of a PIM suite to deal > > with database administration tasks of any kind. […] > > I agree. That is why I switched to the SQLite backend (it, also, is an > improvement over the default MySQL). There are all kinds of warnings > strewn around the internet that it isn't up to the task for Akonadi, > but any issues I have are never reducible to SQLite. It's (failed) > syncing to and from the remote that typically causes problems for me, > because Akonadi doesn't seem capable of recovering. (It seems to use > some out-of-database files thrown into the configuration directory > for the backlog of unsynced local stuff…) Interesting view point. Thanks for this. > A PIM suite needs some database backend for searching and filtering. > But something like SQLite should be up to the task in the > single-user-at-a-time case. (‘Ad’ from sqlite.org: “For device-local > storage with low writer concurrency and less than a terabyte of > content, SQLite is almost always a better solution. SQLite is fast > and reliable and it requires no configuration or maintenance. It > keeps things simple. SQLite "just works".”) It is used in many > applications that put quite some load on it. It includes many > features that could be leveraged (views, triggers, full text search, > json fields). Yeah, I see Firefox uses it all over the place for example. Never had issues with it. But then Firefox databases are usually way smaller. But I use Quassel IRC Core with SQLite on my server and this is 800 MiB database meanwhile. -- Martin