[Zope-dev] PathIndex doesn't index last part of path
sean.upton@uniontrib.com
sean.upton@uniontrib.com
Wed, 21 Aug 2002 08:49:27 -0700
I'm all for putting together a proposal to do this, soliciting comments, and
contributing to the effort. What would be the right venue for that?
On the other hand, AFAIK, the addition of a depth query feature to PathIndex
as it is wouldn't likely break existing indexes. And given that Andy's need
(get metadata for a Cataloged object, given some cached referecne, in this
case a path, to it) could be filled by the Catalog itself (or changes to
it), I'm not sure what other features would be needed out of PathIndex?
In brief, what I would like:
results = Catalog.searchResults(path={'query':myContainersPath,
'depth':0, 'level':0})
Where depth means:
-1 In parent of path specified (up one)
0 Contained within path specified
1 Contained in path specified or directly in one of its
children
2 Same as above, but also in child container's child
No depth specified means behavior is like current functionality in path
indexes. A brief glance at docs and code gives me the impression that this
could peacefuly co-exist with level.
Sean
-----Original Message-----
From: Andreas Jung [mailto:andreas@andreas-jung.com]
Sent: Monday, August 19, 2002 11:14 PM
To: sean.upton@uniontrib.com; casey@zope.com; andy@agmweb.ca;
zope-dev@zope.org
Subject: Re: [Zope-dev] PathIndex doesn't index last part of path
----- Original Message -----
From: <sean.upton@uniontrib.com>
To: <casey@zope.com>; <andy@agmweb.ca>; <zope-dev@zope.org>
Sent: Tuesday, August 20, 2002 00:58
Subject: RE: [Zope-dev] PathIndex doesn't index last part of path
>
> One thing that seems to be feature-broken about PathIndexes, though, is
the
> lack of ability to specify a depth (not level, but depth of a match, for
> example, to specify items). Above and beyond support for a specific place
> within a hierarchy, there needs to be a simple mechanism to support query
> for an absolute path, and only objects directly matching that path, or
> directly contained within that path.
>
Following this thread I appears to me that there is a need for several
new functionalities inside the PathIndex (maybe a new PathIndexNG). In
this case I suggest to write a proposal to collect all requirements.
I volunteer to help on the implementation.
Andreas
_______________________________________________
Zope-Dev maillist - Zope-Dev@zope.org
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )