I think we want to apply the following patch to make the NumberValueRangeProcessor documentation (a) make sense, and (b) accurate: ---------------------------------------------------------------------- --- include/xapian/queryparser.h (revision 9993) +++ include/xapian/queryparser.h (working copy) @@ -213,7 +213,7 @@ * * For example, if str_ is "$" and prefix_ is true, and the range * processor has been added to the queryparser, the queryparser will - * accept "$10..50" or "$10..50", but not "10..50" or "10..$50" as valid + * accept "$10..50" or "$10..$50", but not "10..50" or "10..$50" as valid * ranges. If str_ is "kg" and prefix_ is false, the queryparser will * accept "10..50kg" or "10kg..50kg", but not "10..50" or "10kg..50" as * valid ranges. ---------------------------------------------------------------------- J -- /--------------------------------------------------------------------------\ James Aylett xapian.org james at tartarus.org uncertaintydivision.org
Richard Boulton
2008-Jan-21 09:33 UTC
[Xapian-devel] NumberValueRangeProcessor documentation
On Mon, Jan 21, 2008 at 07:40:35AM +0000, James Aylett wrote:> I think we want to apply the following patch to make the > NumberValueRangeProcessor documentation (a) make sense, and (b) > accurate:I agree. (This email brought to you via the free national express wifi service on the east coast main line - laggy but functional!) -- Richard
On Mon, Jan 21, 2008 at 07:40:35AM +0000, James Aylett wrote:> I think we want to apply the following patch to make the > NumberValueRangeProcessor documentation (a) make sense, and (b) > accurate: > [...] > - * accept "$10..50" or "$10..50", but not "10..50" or "10..$50" as valid > + * accept "$10..50" or "$10..$50", but not "10..50" or "10..$50" as validFeel free to commit... Cheers, Olly