[horde] Shortening Histories

[Michael J Rubinsky]

Quoting Jan Schneider <jan at horde.org>:

> Zitat von Ralf Lang <lang at b1-systems.de>:
>
>> Over the years, the Horde_Histories table can become quite large.  
>> It may make sense to sort out entries we won't need anymore
>>
>> * Entries for users or items which have disappeared, been deleted  
>> outside of horde or directly on the backend
>> * Changes so far past that we don't care anymore
>>
>> If I read the code correctly, ActiveSync completely relies on its  
>> own tables and does not need very old history entries.
>>
>> The listBy code in Turba, Kronolith, Nag and Mnemo relies on  
>> histories to detect changes made at certain points or intervals in  
>> time
>>
>> Imp optionally writes a mail creation log but I don't know if  
>> anything consumes it.
>>
>> Will anything break if I delete far-past histories? I'd use code,  
>> not bare DB statements.
>
> I'm pretty sure ActiveSync still uses Horde_History

Correct.

> and DAV definitely does. What you lose if you delete old entries, is  
> that users that haven't synced since then, but do after you deleted  
> the entry, won't get the changes.
>
> -- 
> Jan Schneider
> The Horde Project
> https://www.horde.org/
>
> -- 
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org



-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3282 bytes
Desc: S/MIME Signature
URL: <https://lists.horde.org/archives/horde/attachments/20170109/a09e2bc1/attachment-0001.bin>