[ZO-Coll] [ZOC] 397/ 4 Comment "Patch for making PathIndex sortable"

[Collector: NEW Zope.org (the ...]

Issue #397 Update (Comment) "Patch for making PathIndex sortable"
 Status Pending, searching/feature medium
To followup, visit:
  http://www.zope.org/Collectors/ZopeOrg/397

==============================================================
= Comment - Entry #4 by nickbower on Mar 6, 2006 8:57 pm

Sorry - please close this.  I'll re-raise it on the other collector.

I obviously read "zope.org development" a different way to which it was intended.

Thanks!
________________________________________
= Comment - Entry #3 by camil7 on Mar 3, 2006 6:11 pm

Maybe its on nobodys radar, because its in the wrong collector?

This collector is for issues with the website www.zope.org

The collector for the zope software is here:
 http://www.zope.org/Collectors/Zope
________________________________________
= Comment - Entry #2 by nickbower on Mar 2, 2006 9:30 pm

[bounce]

...taking the time to submit a patch would usually warrant a response on the ticket?

________________________________________
= Request - Entry #1 by nickbower on Feb 16, 2006 12:36 am


Uploaded:  "PathIndex.patch"
 - http://www.zope.org/Collectors/ZopeOrg/397/PathIndex.patch/view
PathIndex (in PluggableIndexes) is not sortable because it doesn't inherit from the PluggableIndexes/common/UnIndex.py (like FieldIndex etc do).  I can see no bvious reason why it couldn't be sortable hoewver as it still implements inverse lookups using self._unindex which is an IOBTree.

I have produced a patch and attach it here.  Unit tests ran fine and when using it, PathIndex won't barf when you supply the "sort_on" attribute to a catalog search on on this index.

Could this be considered for inclusion into the next zope release?

==============================================================