RE: [Zope-dev] ZCatalog features> I think that the idea of exposing these _in addition_ to (as opposed to instead
of) the current way it works is a good idea.
What does "these" refer to here? if you mean intersection and union operations, this is the plan.
How hard would it be to add the current 'user visible' boolean logic to field types other than text?
I'm not sure what you mean... what feature are you referring to? Thanks! - C -----Original Message----- From: Chris McDonough [mailto:chrism@digicool.com] Sent: Saturday, 28 April 2001 17:10 To: Morten W. Petersen Cc: zope-dev@zope.org Subject: Re: [Zope-dev] ZCatalog features "Morten W. Petersen" wrote:
Hia guys,
A couple of comments and questions about the ZCatalog:
Is it possible to pass an argument to the catalog so that returned brains would instead be actual objects?
Not currentl, although the new brain objects have a method 'getObject' that makes getting the object straightforward while you're iterating over a bunch of them.
Given that we have to manually join search results, because ZCatalog doesn't support ORs etc (for FieldIndexes), wouldn't it be useful to have some sort of tool that could take a set of results, and return a result with only unique values? Yes. There's a propsal on dev.zope.org to expose union and intersection operations to users of the catalog. http://dev.zope.org/Wikis/DevSite/Proposals/UnionAndIntersectionOperations . Comments are appreciated.
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 )