Hello, Ritu Kedia <[EMAIL PROTECTED]> writes:
> Need some help in understanding the RDBMS Schema of Slide:: > > When we put a non-versioned file under version control a new URI entry is > made for the versioned counterpart (history/#) > How is the URI entry of the original non-versioned file bound to its > versioned counterpart ? In other words if the URI_ID of the non-versioned > file is 30 and that of the versioned-counterpart 35, then how are these 2 > linked? The Parent_Binding and Binding tables show the association between > the parent collection and the non-versioned file but there is no binding > present between the non-versioned file and the history entry of its > versioned counterpart. Could someone please point out what am I missing? WebDAV versioning and slide versioning do not work that smooth together. DeltaV is implemented on top of the slide API. The connection between the resource at /files and the resources at /history are made by properties. /files/foo.c has a property "checked-out", which points to something like <D:href xmlns:D="DAV:">/history/32212/1.1</D:href>. For the exact meaning of the related properties look into the DeltaV specification. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
