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

[Ingo Klöcker]

On Tuesday 29 November 2011, Dmitry Torokhov wrote:
> Hi,
> 
> So I have upgraded from very usable setup with Fedota 15/KDE 4.6.x to
> Fedora 16 with shiny new KDE 4.7.3 and brand new KDE PIM suite and as
> many users found that the new version Akonadi/Kmail2 is pretty much
> unusable. The conversion of my archive mailbox (mixed maildir) and 2
> IMAP accounts ran for over 8 hours and I am not quite sure what state
> it is in the moment as Kontact is trying to open my work mailbox for
> over 10 minutes now (ever since I got to my desk and woke up my
> laptop).
> 
> Looking at the Akonadi mysql database I see that I have 3 large
> tables: - parttable:			587230 rows;
> - pimitemflagrelation:		241688 rows;
> - pimitemtable:			294840 rows;

[snip]

> And this brings me to the question: is stuffing everything into a
> single database such a good idea?

Yes. It is. Otherwise something like virtual folders (e.g. all messages 
with certain tags or all messages with certain senders/recipients) would 
be almost impossible to implement. Using a single database one gets this 
feature almost for free.


Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20111205/0f1bd4be/attachment.sig>
-------------- next part --------------
_______________________________________________
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/