Hi Jacob,
you *can* configure Slide s.t. history data of project1 is separated from history data
of project2. You *can* configure your stores s.t. for each project data and history
data are stored together in one DB.
Is that what you need?
If yes, proceed as follows (all in Domain.xml):
1) Set historypath parameter (at the end of Domain.xml) to be /history/${store}
2) Configure a default store (e.g. TX filesystem store) with scope matching "/"
3) Configure the project1 store (e.g. MySQL store) with scope matching
"/files/project1" and database="DB1"
4) Configure the history1 store with scope matching "/history/project1" and
database="DB1"
5) Configure the project2 store with scope matching "/files/project2" and
database="DB2"
6) Configure the history2 store with scope matching "/history/project2" and
database="DB2"
7) Initialize all of the nodes /files, /files/project1, /files/project2, /history,
/history/project1, /history/project2 (within the <data> element)
If needed, proceed in the same manner with workspace and workingresource data.
Regards,
Peter
> -----Original Message-----
> From: Jacob Lund [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 03, 2004 14:11
> To: 'Slide Developers Mailing List'
> Subject: structure of History and how to clean up
>
>
> Hi!
>
> One of my concerns with slide in production is the handling of history
> versions.
>
> How do I clean up in my history files?
>
> I would really like to keep the collection hierarchy between
> /files and
> /history. That way I would be able to separate a collection
> and its history
> versions in the same database.
>
> E.G.: /files/project1 and /history/project1 are directed to the same
> database in domain.xml. When project1 is no longer necessary
> I can simply
> delete this part and both files and history will be cleaned up.
>
> Another way could be the possibility of defining a separate
> history uri to
> each store.
>
> I do not believe that this would be a problem with respect to
> the deltaV
> standard.
>
> /Jacob
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
