How to choose: Or, Not and And when using searchResults().
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?
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 calls and what not?
_______________________________________________ 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 )
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"?
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 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 wanted to try to implement it, they could create a fishbowl project and I can provide assistance.
Oh, and by the way, "searchRequest"?
__call__ works too. ;-) - C
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 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 wanted to try to implement it, they could create a fishbowl project and I can provide assistance.
Oh, and by the way, "searchRequest"?
__call__ works too. ;-)
- C
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 to implement this exists in various places, it really just needs fleshing out and tying together. I have also been waiting for the ZCatalog changes that have just taken place in 2.3.1. Now that this has happened, it may be a good time to start the discussion in the Fishbowl. I would be willing to draft this proposal, but it will be a few weeks before I realistically can do it. -- | Casey Duncan | Kaivo, Inc. | cduncan@kaivo.com `------------------>
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 to implement this exists in various places, it really just needs fleshing out and tying together.
I totally agree.
I have also been waiting for the ZCatalog changes that have just taken place in 2.3.1. Now that this has happened, it may be a good time to start the discussion in the Fishbowl. I would be willing to draft this proposal, but it will be a few weeks before I realistically can do it.
If you'd be willing to take it on, I think many people would give you attaboys for years to come! ;-) It doesn't seem to be on the roadmap here, so if you choose to write the proposal, I'll help in any way I can by review or contributing code. 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
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 am approaching from a fairly selfish perpective. It would just make Zope that much better for me to use! Plus I think it would be a fun, doable and useful project. -- | Casey Duncan | Kaivo, Inc. | cduncan@kaivo.com `------------------>
participants (3)
-
Casey Duncan -
Chris McDonough -
Erik Enge