If you call getObject, that actually does traversal anyway.
Right, in that situation it would be pointless...
You rock, Casey, thanks. I was thinking more about adding:
def getMetadataFromPath(self, path):
get metadata for an object using its path
rid = self._catalog.uids[path]
Your code looks fine, I think it meshes better with the underlying catalog
code too. I don't have a problem with this getting checked in, just make
sure you update IZCatalog.py, help/Catalog.py and add unit tests (that pass
;^).
-Casey
- Original Message -
From: Andy McKay [EMAIL
Woohoo my first check in ;)
--
Andy McKay
Agmweb Consulting
http://www.agmweb.ca
- Original Message -
From: Casey Duncan [EMAIL PROTECTED]
To: Andy McKay [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Saturday, August 17, 2002 12:14 PM
Subject: Re: [Zope-dev] PathIndex doesn't index
Casey Duncan writes:
A PathIndex is designed to make it more efficient to aggregate objects at
various levels of containment. Their primary use case AFAIK is to allow to
to limit queries to particular places within a hierarchy. The idea is to
eliminate recursive searching of leaf level
Hi,
Sorry, maybe I'm too late ;) but I have a note here.
uid in Cataloc can be path but it can be any arbitrary unigue
identifier. In system I'm working with it is ID generated in the time of
object creation and it persists and it is uid in Catalog. Nothing wrong
with the methods themselves
Yes I agree, I think it would be better if the apis were getRecordForUid,
getIndexForUid since the uids can be something other than paths.Thanks for
the input on that.
-Casey
- Original Message -
From: Myroslav Opyr [EMAIL PROTECTED]
To: Casey Duncan [EMAIL PROTECTED]
Cc: Andy McKay
