Chris McDonough wrote:
dtml-in "Catalog(textindex='foo' AND fieldindex='bar' OR
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?!
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 searchResult
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"?
___
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 precedence in
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
someone
BTW, it *is* possible to use AND, NOT, OR, and ANDNOT in the body of a
textindex query, e.g.
dtml-in "Catalog(textindex="foo and bar or farfoo andnot flea")
This is not a problem.
But the original question (and what is not possible currently), is how
to do something like:
dtml-in
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 no concrete plans
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 work
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 proposal, I