On Jan 29, 2007, at 6:15 PM, Chris Hostetter wrote:
: > We override defaultOperator of "OR" to "AND".
:
: We really ought to make AND the default anyway.
No, no, no, no, Nooooooooooooo......
:)
Your argument is a good one, and I buy it. However, I've never had a
case where a user typing "multiple words" where the expectation was
for OR, it is always AND. Thanks to it being configurable this is
not a problem with &q.op=AND, though that setting will be in every
app I build (and will be the default in solrb's Request::Standard,
probably).
Erik
there is no prefix operator for "OR" so if the default is "AND"
there is
no way at request time to indicate that some clauses should be
optional
without reverting to the ugly and missleading binary operator
syntax ...
if the default is "OR" then you *can* add the prefi "+" to indicate
which
clauses are mandatory.
I'm fully on board having it configurable and letting people change
it --
but OR really should stay the default.
