> 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
Given a method that you could return a catalog record given a path (which is
an obj's ZCatalog uid), then this would be faster then traversal I think
(probably a lot faster). So long as whatever you wanted could be gotten from
metadata. If you call getObject, that actually does traversal anyway.
[snip]
Hmm ok, I can see those reasons.
> Unfortunately, ZCatalog does not expose this to the surface but you
> can write a trivial external method to do it. And I might entertain adding
a
> ZCatalog API to do so if I had a good use case.
Ah... I think this might be the best idea, I'll add that
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 folders when you want all
object
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 folders when you want all
object
This is mostly a question for AJ, but any input would be great. This bug bit
me today and is documented here:
http://collector.zope.org/Zope/449/ISSUE_TRANSCRIPT/view
I dont understand the brief argument against this one, it would make sense
to me to able to pull an object out of the catalog base