[Zope-dev] ZCatalog features

Mon, 30 Apr 2001 09:35:31 -0700

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0D193.940FA7D0
Content-Type: text/plain;
	charset="iso-8859-1"

Sorry... a user came into the office as I was writing that email and
completely broke my train of though :( grrrr...

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...

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?

Adrian...

-----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 )

------_=_NextPart_001_01C0D193.940FA7D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: [Zope-dev] ZCatalog features</TITLE>
</HEAD>
<BODY>

Sorry... a user came into the office as I was writing =
that email and completely broke my train of though :( grrrr...

<P><FONT SIZE=3D2>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...</FONT></P>

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?

<P><FONT SIZE=3D2>Adrian...</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Chris McDonough [<A =
HREF=3D"mailto:chrism@digicool.com">mailto:chrism@digicool.com</A>]</FON=
T>
<BR><FONT SIZE=3D2>Sent: Monday, 30 April 2001 17:17</FONT>
<BR><FONT SIZE=3D2>To: Adrian Hungate</FONT>
<BR><FONT SIZE=3D2>Cc: zope-dev@zope.org</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Zope-dev] ZCatalog features</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>RE: [Zope-dev] ZCatalog features&gt; I think that the =
idea of exposing these</FONT>
<BR><FONT SIZE=3D2>_in addition_ to (as opposed to instead</FONT>
<BR><FONT SIZE=3D2>&gt; of) the current way it works is a good =
idea.</FONT>
</P>

<P><FONT SIZE=3D2>What does &quot;these&quot; refer to here?&nbsp; if =
you mean intersection and union</FONT>
<BR><FONT SIZE=3D2>operations, this is the plan.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; How hard would it be to add the current 'user =
visible' boolean logic to</FONT>
<BR><FONT SIZE=3D2>field</FONT>
<BR><FONT SIZE=3D2>&gt; types other than text?</FONT>
</P>

I'm not sure what you mean... what feature are you =
referring to?

<P><FONT SIZE=3D2>Thanks!</FONT>
</P>

<P><FONT SIZE=3D2>- C</FONT>
</P>
<BR>

-----Original Message-----
 From: Chris McDonough [<A =
HREF=3D"mailto:chrism@digicool.com">mailto:chrism@digicool.com</A>]</FON=
T>
 Sent: Saturday, 28 April 2001 17:10
 To: Morten W. Petersen
 Cc: zope-dev@zope.org
 Subject: Re: [Zope-dev] ZCatalog features

&quot;Morten W. Petersen&quot; wrote:
 &gt;
 &gt; Hia guys,
 &gt;
 &gt; A couple of comments and questions about the =
ZCatalog:
 &gt;
 &gt; Is it possible to pass an argument to the =
catalog so that returned brains
 &gt; 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.
 &gt; Given that we have to manually join search =
results, because ZCatalog
 &gt; doesn't support ORs etc (for FieldIndexes), =
wouldn't it be useful to have
 &gt; some sort of tool that could take a set of =
results, and return a result
 &gt; with only unique values?
 Yes.&nbsp; There's a propsal on dev.zope.org to =
expose union and intersection
 operations to users of the catalog.
 <A =
HREF=3D"http://dev.zope.org/Wikis/DevSite/Proposals/UnionAndIntersection=
Operations" =
TARGET=3D"_blank">http://dev.zope.org/Wikis/DevSite/Proposals/UnionAndIn=
tersectionOperations</A>
 .&nbsp;&nbsp; Comments are appreciated.
 _______________________________________________
 Zope-Dev maillist&nbsp; -&nbsp; =
Zope-Dev@zope.org
 <A =
HREF=3D"http://lists.zope.org/mailman/listinfo/zope-dev" =
TARGET=3D"_blank">http://lists.zope.org/mailman/listinfo/zope-dev</A></F=
ONT>
 **&nbsp; No cross posts or HTML encoding!&nbsp; =
**
 (Related lists -
 &nbsp;<A =
HREF=3D"http://lists.zope.org/mailman/listinfo/zope-announce" =
TARGET=3D"_blank">http://lists.zope.org/mailman/listinfo/zope-announce</=
A>
 &nbsp;<A =
HREF=3D"http://lists.zope.org/mailman/listinfo/zope" =
TARGET=3D"_blank">http://lists.zope.org/mailman/listinfo/zope</A> =
)

</BODY>
</HTML>
------_=_NextPart_001_01C0D193.940FA7D0--