[Kde-pim] Akonadi: single database design mistake?

[Andras Mantia]

bhlevca wrote:

> What I mean by database centric is not the mysql database, but the
> akonadi/nepomuk/virtuoso handling everything.
> As you pointed out mysql is actually doing fine. That is just a backend
> which can be switched to sqlite or postgres.
> 
That is why I said your mail in this form is no more but a rant, because you 
don't know what is the problem. What if it turns out the problem is 
communication between components? What if the problem turns to be in the 
*client* applications? 

Using databases behind them is just not relevant or might be not relevant. 
If you'd question the distributed design and the complexity of the system, 
that would be slightly better, but still too vague.

And I'm sorry if I sounded rude, especially is I am *aware* of the pain 
users had and I know we have some issues to fix, but your mail was not 
constructive at all and was not offering any solution (searching is only 
part of the system and the akonadi database is there *not* for searching) or 
analysis (mind you, on a devel list). Neverthless throwing away and coming 
up with something new is not the way to go (for many reasons, be it 
technical or not).

Andras
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/