Roman D wrote:
I was looking for something similar, but since it's not a part of Webdav
protocol, it'll never be in Slide.
I take URI and find database object by splitting it, then you can find
your unique ID from DB object.
Problem with this approach is that the ID changes on move/rename,
On Thu, 09 Dec 2004 09:08:56 +0100, Guido Casper [EMAIL PROTECTED] wrote:
I always wanted to have a take at a ID-preserving intra-store move
operation but unfortunately lack the time currently.
I have already implemented this move, copy and delete in the current CVS head.
Oliver
Oliver Zeigermann wrote:
On Thu, 09 Dec 2004 09:08:56 +0100, Guido Casper [EMAIL PROTECTED] wrote:
I always wanted to have a take at a ID-preserving intra-store move
operation but unfortunately lack the time currently.
I have already implemented this move, copy and delete in the current CVS head.
I was looking for something similar, but since it's not a part of Webdav
protocol, it'll never be in Slide.
I take URI and find database object by splitting it, then you can find
your unique ID from DB object.
Nick Longinow wrote:
Hi
It seems that the uri for a document (resource) in the
Using an event listener you could set a GUID on each resource as it is
created, or if you have a custom store you could expose the unique ID as
a property. Of course, the only way to *retrieve* an object based on the
value of this property is through a search, so I don't know how useful
it would
