diff --git a/src/doc/user/usermanual.html b/src/doc/user/usermanual.html index 371bc7a4..b9ba51da 100644 --- a/src/doc/user/usermanual.html +++ b/src/doc/user/usermanual.html @@ -265,6 +265,9 @@ alink="#0000FF">
3.6.1. Range + clauses
+
3.6.2. Modifiers
@@ -4089,7 +4092,7 @@ alink="#0000FF"> set.

  • -

    %t. Title.

    +

    %t. Title or empty.

  • %U. Url

    @@ -4639,7 +4642,7 @@ alink="#0000FF">

    Modifiers can be set on a double-quote value, for example to specify a proximity search (unordered). See the modifier section. No space + "3.6.2. Modifiers">the modifier section. No space must separate the final double-quote and the modifiers value, e.g. "two one"po10

    @@ -4891,13 +4894,50 @@ alink="#0000FF"> use OR with ext terms for example.

    +
    +
    +
    +
    +

    3.6.1. Range + clauses

    +
    +
    +
    +

    Recoll 1.24 and later + support range clauses on fields which have been + configured to support it. No default field uses them + currently, so this paragraph is only interesting if you + modified the fields configuration and possibly use a + custom input handler.

    +

    A range clause looks like one of the following:

    + 
    myfield:small..big
+myfield:small..
+myfield:..big
+
    +

    The nature of the clause is indicated by the two dots + .., and the effect is to + filter the results for which the myfield value is in the + possibly open-ended interval.

    +

    See the section about the fields configuration file for the + details of configuring a field for range searches.

    +

    3.6.1. Modifiers

    + "RCL.SEARCH.LANG.MODIFIERS">3.6.2. Modifiers
    @@ -5937,6 +5977,12 @@ alink="#0000FF"> and other aspects of fields handling is defined inside the fields configuration file.

    +

    Some fields may also designated as supporting range + queries, meaning that the results may be selected for an + interval of its values. See the configuration section for + more details.

    The sequence of events for field processing is as follows:

    @@ -9134,6 +9180,17 @@ for i in range(nres): extension prefixes should be all caps, begin with XY, and short. E.g. XYMFLD.

    +
    [calues]
    +
    +

    Fields listed in this section will be stored as + Xapian + values inside the + index. This makes them available for range queries, + allowing to filter results according to the field + value. This feature currently supports string and + integer data. See the comments in the file for more + detail

    +
    [stored]

    A field becomes stored (displayable inside diff --git a/src/doc/user/usermanual.xml b/src/doc/user/usermanual.xml index 5530d1fd..b6192e07 100644 --- a/src/doc/user/usermanual.xml +++ b/src/doc/user/usermanual.xml @@ -3794,6 +3794,34 @@ OR with ext terms for example. + + Range clauses + + &RCL; 1.24 and later support range clauses on fields which + have been configured to support it. No default field uses them + currently, so this paragraph is only interesting if you modified + the fields configuration and possibly use a custom input + handler. + + A range clause looks like one of the following: + myfield:small..big +myfield:small.. +myfield:..big + + + The nature of the clause is indicated by the two dots + .., and the effect is to filter the results for + which the myfield value is in the + possibly open-ended interval. + + See the section about the + fields configuration file for the + details of configuring a field for range searches. + + + + Modifiers @@ -4638,6 +4666,11 @@ other aspects of fields handling is defined inside the fields configuration file. + Some fields may also designated as supporting range queries, + meaning that the results may be selected for an interval of its + values. See the + configuration section for more details. + The sequence of events for field processing is as follows: During indexing, @@ -6211,6 +6244,16 @@ for i in range(nres): caps, begin with XY, and short. E.g. XYMFLD. + + [calues] + Fields listed in this section will be stored as + &XAP; values inside the index. This makes + them available for range queries, allowing to filter results + according to the field value. This feature currently supports + string and integer data. See the comments in the file for more + detail + + [stored] A field becomes stored (displayable inside