[horde] Shortening Histories

Jan Schneider jan at horde.org
Mon Jan 9 20:19:05 UTC 2017


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, 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/



More information about the horde mailing list