Hi,

As a Gentoo user, I got used to Akonadi using SQLite as a backend, and now am setting it as default on all accounts I use (Chakra on my laptop).
My question is : why is it "not recommended" to use Akonadi with SQLite? I've been using this setup for about a year now, and am a happy camper.

The only issue I could find (concurrent writes) has been solved by SQLite implementing WAL (Write Ahead Logging). Maybe there are still some performance issues I'm not aware of (haven't done any benchmarking)?

Thanks,

Serafean

You might want to defer to an email to kde-pim@kde.org (the PIM developers list) in regards to this.
I believe it was related to Atomicity/Concurrency/Parallel operations however.

Akonadi with SQLite was done, IIRC, to ensure that Kontact would work on limited capability devices - Windows CE phones, to be precise. However, even if SQLite is thread-safe, there are still large issues with concurrency, which Akonadi needs. Also, testing has showed deadlocks and problems with transactions.

Hi,

Thanks for your answers. I guess I'll continue being brave using SQLite as backend since I haven't encountered any noticeable issues (yet).

Serafean