>> I like the idea to use a DB for storing cache data. May be it is a good
>> idea to store config data in a DB as well, but I an not sure that it is
>> a good idea to store configuration and cache data in the same DB (IMHO
>> it is a bad idea).
> What is the configuration data that is stored in the DB?
I don't know. But in the named thread from December last year a
developer made clear that deleting the akonadi DB is a really bad idea.
If this DB stores cached data only this should not be any problem. So it
is my guess that there are config data stored in the DB as well.
>> I am not sure that I understand the SizeThreshold parameter. Is this the
>> amount of data (MBytes or data sets) that are stored in the cache DB?
>> What are the consequences if I set this value to 0 or a even higher
>> value than the default.
> Its unit is bytes, i.e. size of payload parts (which in turn depend on the
> data type, e.g. a full contact or headers of an email or full email, etc).
> All content that is above the threshold is cached in files, all content up to
> the threshold is cached in the DB.
OK, thanks for the explanation. Where are the cache files located? Can I
exclude them from backup/sync?
>>> Please keep in mind that content that is not uploaded to the respective
>>> storage location yet will be lost if you only backup the DB in such
>>> P.S.: if $XDG_CONFIG_HOME is not set the specified default is