Chris McDonough wrote:
>
> keywordindex=['flop'])">
>
Chris, how hard would it be to expose ZCatalog's set lazy union and intersection
operators?
IIRC, ZCatalog does a lot of this internally so it shouldn't be that hard to do?
(right?! ;-)
If you could expose it, then you could construct th
Chris McDonough wrote:
>
> BTW, some changes are coming to the way we allow contributions to the Zope
> codebase which have the potential to reduce the DC "drag factor" for this
> and other similar projects.
>
> - C
I await this process change with great curiousity.
As for the ZCatalog proposa
> This is a project I have been keeping in the back of my mind for a while
> now. At present I do not have the resources to devote, but it is my hope
> that this will change. I feel strongly that that ZCatalog should have a
> general query language on par with an SQL where clause. Much of the wor
Chris McDonough wrote:
>
> Erik Enge wrote:
> >
> > On Wed, 18 Apr 2001, Chris McDonough wrote:
> >
> > > You need to manually do unions or intersections on results from multiple
> > > calls to searchRequest currently.
> >
> > Is this a feature to be implemented? If not, why not?
>
> DC has no
BTW, it *is* possible to use AND, NOT, OR, and ANDNOT in the body of a
textindex query, e.g.
This is not a problem.
But the original question (and what is not possible currently), is how
to do something like:
...currently the best you can do is:
...
... which does an implicit inters
Marco Nova wrote:
> > DC has no no concrete plans to implement operators or precedence in
> > catalog queries, although I think it's a really
> > super-worthwhile idea.
> > We're currently focusing on the things in the Zope 2.4 plan (see
> > http://dev.zope.org/Resources/zope_240_plan.html). If
>
> > On Wed, 18 Apr 2001, Chris McDonough wrote:
> >
> > > You need to manually do unions or intersections on
> results from multiple
> > > calls to searchRequest currently.
> >
> > Is this a feature to be implemented? If not, why not?
>
> DC has no no concrete plans to implement operators or
Erik Enge wrote:
>
> On Wed, 18 Apr 2001, Chris McDonough wrote:
>
> > You need to manually do unions or intersections on results from multiple
> > calls to searchRequest currently.
>
> Is this a feature to be implemented? If not, why not?
DC has no no concrete plans to implement operators or
On Wed, 18 Apr 2001, Chris McDonough wrote:
> You need to manually do unions or intersections on results from multiple
> calls to searchRequest currently.
Is this a feature to be implemented? If not, why not?
Oh, and by the way, "searchRequest"?
__
No, unfortunately.
You need to manually do unions or intersections on results from multiple
calls to searchRequest currently.
Erik Enge wrote:
>
> Hi,
>
> I was wondering, is there a way I can choose whether I want searchResults
> to Or, Not or And the search? Or do I need to combine searchRe
Hi,
I was wondering, is there a way I can choose whether I want searchResults
to Or, Not or And the search? Or do I need to combine searchResult calls
and what not?
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zo
11 matches
Mail list logo
