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

[Kevin Krammer]

On Monday, 2013-03-04, Lindsay Mathieson wrote:

> Also 5) Cache gets out of sync.
> 
> If as you say its a cache, then it is inevitably prone to the usual cache
> problems of getting out sync, either due to user or developer error
> - unforeseen edge cases, environmental issues or plain old bugs. With any
> other cache system that I'm aware of you just delete or clear the cache and
> let it refresh itself and everyone is happy, users and developers.
> 
> But with akonadi that will lead to major ui and data loss issues and I just
> don't understand this insistence on keeping it this way. Your approach
> seems to be "This will never happen", but it does. And will.
> 
> That the "cache" generates unique id's - that have to be used by external
> modules such as the filters says to me that its not really a cache. And the
> Id's are not unique as they are reused if the cache is cleared, leading to
> this whole issue of filters getting messed up. Also the special folders
> such as drafts, trash etc.

The item ids are not affected when the cache is cleared, each cache item has 
its own id and has a reference to the item it belongs to.

The problem is that people are not clearing the cache but removing all data, 
like removing $HOME to clear things in $XDG_CACHE_HOME.

> A proposal  of using Id's generated from the actual FQ folder paths has
> been suggested, which are actually unique. I don't understand
> the resistance to this. It make the akonadi db a true cache and preserve
> peoples configs in case of issue with the db.

The db contains a cache and the cache can be cleared without affecting the 
rest of the data in the db.

The problem is removing all data, like removing all of $HOME just to clear 
$XDG_CACHE_HOME.
Filesystem recovery might help to restore the stuff outside of 
$XDG_CACHE_HOME, however the real solution is to not remove things one does 
not want removed.

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- 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/20130304/934a17c0/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/