On 10/14/2011 05:16 PM, Andras Mantia wrote:
Bruno Friedmann wrote:
On 10/13/2011 05:11 PM, Andras Mantia wrote:
Bruno Friedmann wrote:
On 10/13/2011 03:38 PM, Andras Mantia wrote:
Hi,
I'd like to draw the attention to bug 718367, in case it is still the case of shipping Akonadi to be configured to SQLite by default, please reconsider the decision. This will provide sub-optimal performance and in certain cases buggy behavior (hangs) for Akonadi based applications, including KMail2.
Andras
Andras you know that the sqlite choice was also made because there's no upstream solution for the buggy mysql support on nfs home too :-)
[dream on] One unified full semantic database (that can be per user, per computer, per network) for the whole kde desktop. With a nice administrative stack to dig in it, backup, restore, migrate [/dream off]
Ok, I didn't know about the NFS problem (you refer to the unclear shutdown/broken suspend issue, right: https://bugs.kde.org/show_bug.cgi?id=275261 ? ). So you need to make a choice: - use sqlite and make it a problem for everybody - use mysql and those using NFS will have a problem
Right now I'd say even postgresql would be a better choice, but I have no idea how it works on NFS.
Unfortunately, the postgresql is not a solution. If you configure it by hand to use an external database server, akonadi doesn't care and launch it's own instance. (known bug which will be resolved in 4.8 from what was said to me)
Of course there is also a solution (for distributions) to configure a system wide mysql server that puts the database outside of $HOME and Akonadi can use that one as well.
How will you manage several users in that case?
Unfortunately multiple users using the same database is not supported. See http://techbase.kde.org/Projects/PIM/Akonadi#Can_Akonadi_use_a_normal_MySQL_...
(generally the whole FAQ there is interesting and on topic).
Don't over look, that's exactly what I'm talking about ... how to create automatically (mean by rpm/apt install) a separate database for each user. Which is the perfect setup even on desktop with multiple user, avoid several mysql process, logs, etc. With one central database and having tables prefix like $username_akonadi_table that could be a way to do it but yeap in that case, code need to be changed.
Could be a solution for the livecd? Well, the live CD is not using NFS, so no need for workarounds.> Andras The sqlite choice was made due to malfunction of mysql on livecd if my memory is good. Just check this mailing list archive.
-- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org