On Wednesday 22 Jun 2011 13:16:05 you wrote: > On Wednesday 22 June 2011 13:05:31 Mick did opine thusly:
> > Anyway, I noticed that a KDE machine which is using MySQL as a > > backend for Akonadi is not showing any contacts in its address > > book. All other boxen use sqlite3 instead and they do not seem to > > have any noticeable problems. > > > > Could this be a MySQL issue? > > > > PS. All of these PCs run stable KDE. > > A while ago I eventually got my contacts back. I forget the actual > cause now, but I strongly suspect it involved tinkering with mysql, > and this may have broken in turn my calendar. > > I'm going to do one last test before consigning kdepim to the > trashbin: migrate everything to a new user and start with a default > config. If it works, I can migrate the data at my leisure. > > But now, stupid question incoming: > > How you you get akonadi to use sqlite as the backend? There's no, erm, > gui tickbox for that. Yes, that's right, no GUI box to tick because the KDE devs did not like to support sqlite (some of the things they wanted to do were not straight forward under sqlite). The way I did it was to set it up manually in ~/.config/akonadi/akonadiserverrc. This old thread describes how I went about it: http://article.gmane.org/gmane.linux.gentoo.user/224044 This is what my akonadiserverrc looks like today: ================================================ [%General] Driver=QSQLITE SizeThreshold=4096 ExternalPayload=false [QSQLITE] Name=/home/michael/.local/share/akonadi/akonadi.db Host= User= Password= Options= StartServer=false [Debug] Tracer=null ================================================ No MYSQL section in there at all. However, I must issue a Health Warning here. I never had mysql on this machine and did not have to migrate my PIM resources from mysql to sqlite. So YMMV. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
