On Tue, 6 Jan 2009, Graham Perrin wrote:
> Q: In a nutshell, in what way is backup.chex less complete?
In at least two ways:
- Only a subset of your items are backed up (I don't have the details)
- Only the latest version of these items are setup. Your change history
is lost.
The repository keeps old versions of your items so that concurrent change
merging or rollback and repair is possible. Old item versions are discarded
during the weekly purge operation that Chandler suggests.
When comparing directory sizes, be sure to keep in mind that the
__repository__ directory contains some large files that are part of the
underlying Berkeley DB environment. Technically, these don't count towards
the amount of data the repository is storing.
On the other hand, a __repository__.backup directory does not contain these
Berkeley DB environment files and is a much closer measure of the amount of
data in your repository.
> Q: Is backup.chex alone sufficient for an automated upgrade routine?
Not only sufficient but the only way to upgrade your data when a schema
change occurred between Chandler versions.
> Or does the routine read from (a) the .chex plus (b) the old repository
> to produce (c) an upgraded repository?
No, the old repository is not used by the new Chandler.
Andi..
_______________________________________________
[email protected] mailing list
unsubscribe here: http://lists.osafoundation.org/mailman/listinfo/chandler-users
Chandler wiki: http://chandlerproject.org/wikihome
