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. 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. The fact is what I wrote: sqlite is buggy. I run into the mistake of using sqlite once, when I removed my akonadi config and run the opensuse akonadi instead of my self compiled one. And that was patched and used sqlite. I didn't notice for a day or so, but my number of gray hairs went up and couldn't understand why do I get so frequent hangs in KMail and the Akonadi server. Andras -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org