Am 10.01.2013 18:51, schrieb Per Sterner:
> We like to use the CDO OfflineClone and therefore we need branching and auditing. The problem is that our Database is
> growing quickly.
There have been thoughts about using a non-auditing master repository and it seems conceptually possible. Technically
it's probably non-trivial and a lot of work to develop.
Theoretically clones could drop the part of the history that covers the time before the last replication.
CDOWorkspaces, which also enable offline work, are internally based on a local, non-auditing repository and require at
least auditing mode in the remote (master) repository. The same conceptual thoughts about using non-auditing in the
> Is it possible to compact the revision-history in sync with multiple offlineclone nodes?
The major challenge is that a master can not know if and when specific clones will come back to sync their history. But
I could imagine that we store some per-clone infos in the master to be able to calculate a point in time that the last
one all "known" clones have already incorporated into their replica.
In general CDO has no means to compact histories, neither manually nor automatically. In theory you could either send
some SQL queries to the DBStore or write your own IQueryHandler to do whatever you want on the server.