[Akonadi] [Bug 335209] sqlite backend not selected automatically

Daniel Vrátil dvratil at redhat.com
Wed May 28 10:17:44 BST 2014


https://bugs.kde.org/show_bug.cgi?id=335209

Daniel Vrátil <dvratil at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |dvratil at redhat.com
          Component|general                     |server
         Resolution|---                         |INVALID

--- Comment #1 from Daniel Vrátil <dvratil at redhat.com> ---
When there's no configuration, Akonadi falls back to a default backend. The
default backend can be defined during compilation, but when none is defined, it
will choose MySQL. Most distributions don't change this (I only know about
Fedora shipping Akonadi compiled with SQLite as default backend), so most users
get MySQL automagically when they start Akonadi for the first time.

Falling back to another database backend is not a desired behavior. In case
existing MySQL database fails to start for some reason and Akonadi would just
fallback to SQLite and create a new SQLite database, which would just mess up
KMail and other apps.


You can manually configure the backend in Akonadi Server Configuration KCM
(kcmshell4 akonadi) and start Akonadi from there. You should not need to modify
the config files by hand.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Kdepim-bugs mailing list