Boolean filters shouldn't always combine with AND

[Richard Boulton]

Currently, the query parser always combines boolean filter terms together with AND. In addition, it doesn't handle explicit boolean operators usefully (the result is sometimes useful, but not consistently).

The query parser should be modified to combine boolean filter terms with the same prefix together with OR, and then combine those groups with different prefixes together with AND. The query parser should also respect explicit operators, such that (where a and b are boolean prefixes for A and B).

"a:foo a:bar" becomes "Afoo OR Abar" "a:foo b:bar" becomes "Afoo AND Bbar" "a:foo AND a:bar" becomes "Afoo AND Abar" "a:foo OR b:bar" becomes "Afoo OR Abar"

A tricky case is:

"foo OR a:bar" - this could become "foo OR Abar", but the resulting weights may not be useful.

[Richard Boulton]

Patch adding relevant tests to queryparsertest

[Richard Boulton]

Note - Olly pointed out that the patch doesn't handle value range filters correctly (since these don't have a prefix - instead having a slot number).

There's also the issue about what to do about prefixes which have multiple names

• eg, if add_prefix('author', 'A') and add_prefix('writer', 'A') have been

called, what should "author:foo writer:bar" produce? I'm tending towards thinking that "Afoo AND Abar" is appropriate, mainly because it's easier to document, but I'm not fully convinced.

[Richard Boulton]

Implementation of ORring filter terms with the same prefix

[Richard Boulton]

Updated implementation of ORring filter terms with the same prefix

[Richard Boulton]

Further updated patch

[Richard Boulton]

Further update - adds documentation and a test case

[Olly Betts]

Patch applied, so fixed in SVN HEAD.

[Olly Betts]

Fixed in 1.0.1.