[Kde-pim] Marketing blocker collection, DEADLINE: 2013-03-10

[Volker Krause]

On Tuesday 05 March 2013 10:38:26 Andras Mantia wrote:
> Kevin Krammer wrote:
> > This is, however, unrelated to the cache functionality. Clearing the cache
> > does not remove any collections or items, only cached item data.
> > Thus clearing the cache will not result in change of collection ids.
> 
> There is a confusion here. Wolfgand and Sven talks about the *whole* akonadi
> database when they refer to cache, while you talk about the part cache (a
> subset of the database).
> Both of you are right, we use the term cache for both. :)
> 
> So clearing the part cache has normally no sideeffects, while removing the
> whole db and creating it again makes the stored collection ids invalid.

That also needs to be clarified: removing *not* *dirty* parts from the cache 
is safe. Keep in mind that unlike some of the other examples mentioned in this 
thread (thumbnails, web cache, etc) the Akonadi cache is not read-only, it 
contains modifications not yet written to the corresponding backends.

This does of course not mean that recovering from a fully cleaned cache will 
be fast, the whole thing is optimized for e.g. envelope parts to always be 
cached.

regards,
Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20130305/1924c3b8/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/