Re: Is SQLite3 still not recommended?

Daniel Vrátil <[email protected]> Tue, 04 Apr 2023 09:25:31 +0200

Newsgroups	gmane.comp.kde.devel.pim
Message-ID	<5192336.LvFx2qVVIh@bifrost>

Hi,

I think SQLite is a good choice these days. SQLite has made huge progress in 
the past many years since its support has been introduced to Akonadi. The 
documentation on wiki is certainly not up-to-date.

While I was a big advocate for pushing PostgreSQL as the default backend for 
Akonadi in the past, I think nowadays going for anything else than SQLite as 
the default backend is silly. Especially with today's fast SSD drives, I don't 
think a regular user will notice any difference, it might actually turn out to 
be the fastest solution overall.

Coincidentally, I recently learned that the SQLite shared cache mode, which 
Akonadi uses, has been deprecated for a while and WAL mode is now recommended  
for most usecases, so that's something to look into. There might be more new 
features in SQLite that have been introduced in the past years that Akonadi 
could leverage for better performance.

/Dan

On Wednesday, 29 March 2023 19:12:30 CEST Fabio wrote:
> Hi all,
> 
> the Akonadi documentation suggests to prefer MariaDB/MySQL or PostgreSQL
> over SQLite3, for various reasons. Is this still the case? I feel like
> this suggestion is outdated, for a simple desktop use case. Here some hints:
> 
>    * Debian provides the akonadi-backend-sqlite package
>    * This document hasn't been updated in 8 years:
> https://invent.kde.org/pim/akonadi/-/blob/master/README.sqlite
>    * This answer links to a non-existent web page. Again, it feels like
> it hasn't been reviewed in quite some time:
> https://techbase.kde.org/KDE_PIM/Akonadi#Why_not_use_sqlite?
> 
> For a simple desktop use case, the less daemons/services running, the
> better. That's my take.
> 
> Thank you KDE team and keep rocking!
> Fabio.

signature.asc (application/pgp-signature, 833 B)