ehatcher    2003/10/02 20:01:06

  Modified:    xdocs    queryparsersyntax.xml
               docs     queryparsersyntax.html
  Log:
  minor touchup to QueryParser syntax docs
  
  Revision  Changes    Path
  1.6       +7 -5      jakarta-lucene/xdocs/queryparsersyntax.xml
  
  Index: queryparsersyntax.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-lucene/xdocs/queryparsersyntax.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- queryparsersyntax.xml     10 Sep 2003 15:55:04 -0000      1.5
  +++ queryparsersyntax.xml     3 Oct 2003 03:01:05 -0000       1.6
  @@ -25,7 +25,7 @@
               <li>Untokenized fields are best added directly to queries, and not
               through the query parser.  If a field's values are generated 
programmatically
               by the application, then so should query clauses for this field.
  -            Analyzers, like the query parser, are designed to convert human-entered
  +            An analyzer, which the query parser uses, is designed to convert 
human-entered
               text to terms.  Program-generated values, like dates, keywords, etc.,
               should be consistently program-generated.</li>
   
  @@ -102,13 +102,15 @@
           <subsection name="Range Searches">
               <p>Range Queries allow one to match documents whose field(s) values
               are between the lower and upper bound specified by the Range Query.
  -            Range Queries are inclusive (i.e. the query includes the specified 
lower and upper bound).
  +            Range Queries can be inclusive or exclusive of the upper and lower 
bounds.
               Sorting is done lexicographically.</p>
               <source>mod_date:[20020101 TO 20030101]</source>
  -            <p>This will find documents whose mod_date fields have values between 
20020101 and 20030101.
  +            <p>This will find documents whose mod_date fields have values between 
20020101 and 20030101, inclusive.
               Note that Range Queries are not reserved for date fields.  You could 
also use range queries with non-date fields:</p>
  -            <source>title:[Aida TO Carmen]</source>
  -            <p>This will find all documents whose titles are between Aida and 
Carmen.</p>
  +            <source>title:{Aida TO Carmen}</source>
  +            <p>This will find all documents whose titles are between Aida and 
Carmen, but not including Aida and Carmen.</p>
  +            <p>Inclusive range queries are denoted by square brackets.  Exclusive 
range queries are denoted by
  +            curly brackets.</p>
           </subsection>
   
   
  
  
  
  1.19      +7 -5      jakarta-lucene/docs/queryparsersyntax.html
  
  Index: queryparsersyntax.html
  ===================================================================
  RCS file: /home/cvs/jakarta-lucene/docs/queryparsersyntax.html,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- queryparsersyntax.html    10 Sep 2003 15:55:05 -0000      1.18
  +++ queryparsersyntax.html    3 Oct 2003 03:01:05 -0000       1.19
  @@ -135,7 +135,7 @@
               <li>Untokenized fields are best added directly to queries, and not
               through the query parser.  If a field's values are generated 
programmatically
               by the application, then so should query clauses for this field.
  -            Analyzers, like the query parser, are designed to convert human-entered
  +            An analyzer, which the query parser uses, is designed to convert 
human-entered
               text to terms.  Program-generated values, like dates, keywords, etc.,
               should be consistently program-generated.</li>
   
  @@ -409,7 +409,7 @@
           <blockquote>
                                       <p>Range Queries allow one to match documents 
whose field(s) values
               are between the lower and upper bound specified by the Range Query.
  -            Range Queries are inclusive (i.e. the query includes the specified 
lower and upper bound).
  +            Range Queries can be inclusive or exclusive of the upper and lower 
bounds.
               Sorting is done lexicographically.</p>
                                                       <div align="left">
       <table cellspacing="4" cellpadding="0" border="0">
  @@ -430,7 +430,7 @@
       </tr>
       </table>
       </div>
  -                                                <p>This will find documents whose 
mod_date fields have values between 20020101 and 20030101.
  +                                                <p>This will find documents whose 
mod_date fields have values between 20020101 and 20030101, inclusive.
               Note that Range Queries are not reserved for date fields.  You could 
also use range queries with non-date fields:</p>
                                                       <div align="left">
       <table cellspacing="4" cellpadding="0" border="0">
  @@ -441,7 +441,7 @@
       </tr>
       <tr>
         <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" 
height="1" vspace="0" hspace="0" border="0"/></td>
  -      <td bgcolor="#ffffff"><pre>title:[Aida TO Carmen]</pre></td>
  +      <td bgcolor="#ffffff"><pre>title:{Aida TO Carmen}</pre></td>
         <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" 
height="1" vspace="0" hspace="0" border="0"/></td>
       </tr>
       <tr>
  @@ -451,7 +451,9 @@
       </tr>
       </table>
       </div>
  -                                                <p>This will find all documents 
whose titles are between Aida and Carmen.</p>
  +                                                <p>This will find all documents 
whose titles are between Aida and Carmen, but not including Aida and Carmen.</p>
  +                                                <p>Inclusive range queries are 
denoted by square brackets.  Exclusive range queries are denoted by
  +            curly brackets.</p>
                               </blockquote>
         </td></tr>
         <tr><td><br/></td></tr>
  
  
  

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

Reply via email to