[horde] What is horde_histories for?

[Chuck Hagenbuch]

Quoting Otto Stolz <Otto.Stolz at uni-konstanz.de>:

> I think, I should
> - let horde_categories, horde_tokens, horde_users and horde_vfs
>    alone, as they are not used in my configuration (they are empty,
>    in the beta-test installation),
> - let horde_sessionhandler empty, because the new production
>    version of Horde will build up its own session data,
> - copy horde_datatree, horde_datatree_attributes, and
>    horde_datatree_seq from the beta-test installation, because
>    the Horde Data-Tree contains configuration data (mostly
>    access rights),
> - copy horde_prefs and turba_objects from the old production
>    version (complying with the various caveats from docs/UPGRADING),
>    because they contain the users' preferences and private
>    address books, respectively.
>
> Correct, so far?

All sounds fine.

> But what about horde_histories and horde_histories_seq?
>
> Apparently, these tables keep track of modifications to both
> horde and turba data, probaly the horde data-tree and the
> private addressbooks. Right?

Right.

> Now, will Horde, and Turba work without these history data,

Yes, but you'll lose the information about creation dates, last  
modification dates, etc. And if you use syncing, that will break badly.

-chuck

-- 
"we are plastered to the windshield of the bus that is time." - Chris