Version: 4.6 (using KDE 4.5.95) OS: Linux The use of MySQL as the database backend causes all sorts of issues on various configurations, the most significant being NFS home directories. There are also memory footprint issues on resource-constrained machines such as netbooks. In reading the various information on the web, it is unclear why SQLite would not work for Akonadi. The previous KResource was operating with only a file-based backend, so Akonadi should be able to outperform that using SQLite. The current MySQL setup is brittle and seems to have poor performance. What are the open technical issues that are blocking the adoption of SQLite as the default backend? Reproducible: Always
bugs.kde.org is not a forum. Please either report precise issue or use the appropriate way to ask questions: - http://forum.kde.org - https://mail.kde.org/mailman/listinfo/kdepim-users
Let me outline the precise steps to reproduce: 1) Stop Akonadi 2) Edit ~/.config/akonadi/akonadiserverrc 3) Change: Driver=QSQLITE 4) Add: [QSQLITE] Name=/home/USER/.local/share/akonadi/akonadi.db 5) Start Akonadi Akonadi crashes and does not start. This behavior occurs in 1.3.1 (KDE 4.4) on Fedora 12. I will try it later today in 1.4.0 (KDE 4.5) on Kubuntu.
Please use the sqlite driver which is shipped with akonadi. It is called QSQLITE3. Akonadi 1.5 ships with some major improvements for sqlite3 see https://projects.kde.org/projects/kdesupport/akonadi/repository/revisions/1.5/entry/NEWS
Hi Bjoern, I was able to get it working to a basic point on Akonadi 1.4.0. I don't have Akonadi 1.5 readily available, but I assume that the driver would be improved in that version. Therefore, please go ahead and leave this bug as resolved. Thanks for the tip! Kumaran