On Tuesday 08 March 2005 14:46, Erik Hatcher wrote:

> > Right. `a AND (NOT b)'  parses to `a'
>
> Is this what we want to happen for a general purpose next generation
> Lucene QueryParser though?  I'm not sure.  Perhaps this should be a
> ParseException instead?

As we have no concept of a "warning" we should indeed prefer to throw an 
exception instead of silently modifying the query in ways the users don't 
expect.

Regards
 Daniel

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to