[Xapian-tickets] [Xapian] #234: add an option to specify whether filter terms of a given prefix should be ORed or ANDed together

[Xapian]

#234: add an option to specify whether filter terms of a given prefix should be
ORed or ANDed together
---------------------------+------------------------------------------------
 Reporter:  tv+xapian.org  |        Owner:  olly     
     Type:  enhancement    |       Status:  assigned 
 Priority:  normal         |    Milestone:           
Component:  Omega          |      Version:  SVN trunk
 Severity:  minor          |   Resolution:           
 Keywords:                 |    Blockedby:           
 Platform:  All            |     Blocking:           
---------------------------+------------------------------------------------

Old description:

> Hi,
>
> the patch at
> http://people.debian.org/~tviehmann/list-
> search/xapian_omega_add_option_filter_defaultop.diff
> adds an option map to allow overriding the filter behaviour from OR to
> AND among
> the terms of a given prefix.
> For example, if first and last name are indexed with prefix A, I would
> add
>   $setmap{filter_defaultop,A,AND}
> to the query template in order to be handle first, last, or first and
> last name
> entered into the appropriate fields.
>
> Kind regards
>
> Thomas
>
> URL: http://people.debian.org/~tviehmann/list-
> search/xapian_omega_add_option_filter_defaultop.diff

New description:

 Hi,

 the patch at
 http://people.debian.org/~tviehmann/list-
 search/xapian_omega_add_option_filter_defaultop.diff
 adds an option map to allow overriding the filter behaviour from OR to AND
 among
 the terms of a given prefix.
 For example, if first and last name are indexed with prefix A, I would add
   $setmap{filter_defaultop,A,AND}
 to the query template in order to be handle first, last, or first and last
 name
 entered into the appropriate fields.

 Kind regards

 Thomas

 URL: http://people.debian.org/~tviehmann/list-
 search/xapian_omega_add_option_filter_defaultop.diff

--

Comment(by olly):

 This ticket is a different issue really - it's about how Omega builds a
 filter from multiple B CGI parameters, whereas your issue is about the
 !QueryParser's handling of boolean filter terms.  It would be better not
 to hijack this ticket other issue, and there's already #402 for your
 issue.

-- 
Ticket URL: <http://trac.xapian.org/ticket/234#comment:6>
Xapian <http://xapian.org/>
Xapian