[Zope-dev] ZCatalog features

[Chris McDonough]

RE: [Zope-dev] ZCatalog features> What I meant to say was, I think that
access to the Union and Intersection
> operators would be a very useful feature as long as it would not involve
> a change to any other documented APIs etc...

OK, good this is what's specified in the fishbowl proposal (in a number of
ways).

> By user visible, I meant the AND/OR keyword processing in catalog queries
> on textindex fields. Would it be possible/easy to add this to other field
> types?

Not really... the default behavior of field/keyword indexes is to do a union
on the documents that match a list passed in, e.g. ['a', 'b'] matches
documents with either 'a' or 'b' as index elements.  There can be no "and"
for fieldindexes (because they only store one value).  For kw indexes it may
make sense, but is unimplemented.

Drop-in indexes will hopefully solve many of these problems.

-----Original Message-----
From: Chris McDonough [mailto:chrism@digicool.com]
Sent: Monday, 30 April 2001 17:17
To: Adrian Hungate
Cc: zope-dev@zope.org
Subject: Re: [Zope-dev] ZCatalog features


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 )