Re: export and import of repository data

[Eric Johnson]

Seems to me like you still need an "export".  Doesn't "COPY" has the 
potential to drop or change "live" DAV properties that an "export" would 
preserve?  Actually, it seems like COPY may be required to change live 
properties (create time, user, etc.).  Not to mention, in a future 
release, there may be more or fewer live properties, and an 
export/import sequence could address those issues in a way that COPY 
might not.

Does a DAV COPY also apply to the historical data associated via a 
DeltaV revision history?  I've not read the spec closely enough.

-Eric.

Richard Unger wrote:

Forgive me for asking, but should you (theoretically at least) not just be able
to DAV:copy the resources from one store/server to the other?
Richie 

Quoting Oliver Zeigermann <[EMAIL PROTECTED]>:

 

Jacob Lund wrote:

   

I am not sure if I understand you correctly!

If an import/export is based on the file store then you have problems if
     

you
   

want to make changes to this store.
     

Hm, that's right. We could keep this verions of the the file store 
format for later compatibility then, right?

   

An export should be based on a higher layer in slide and thereby
     

independent
   

of the store! The purpose of an export could also be migrating to a newer
version of the same store! 
     

Would be most easy if you follow the procedure proposed before: read the 
whole tree and write it to a second store also configured in Slide. This 
may well be the new version of the old store.

Oliver

   

Jacob

-----Original Message-----
From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] 
Sent: 10. december 2003 11:02
To: Slide Developers Mailing List
Subject: Re: export and import of repository data

Jacob Lund wrote:

     

Just a small question! Has there been any consideration about making an
export and import function in slide! This could be especially interesting
when migrating from one datastore to another!
       

I have thought about this as well. A possible solution would be to have 
the format of the file system store as the export/import format. This 
way you could traverse the full Slide tree using the store to export and 
writing it to the file store. Then you can zip, tar, whatever the folder 
the data is stored in, and traverse it (later) and write the read data 
into the import store. Sounds easy, does it work? I guess, it does...

Comments? Thoughts?

Oliver



---------------------------------------------------------------------
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]
     



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


   





---------------------------
This mail sent through the 
ungerground webmail system

---------------------------------------------------------------------
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]