ConstantScoreRangeQuery can be used for better performance and to override the limit of toomanyclauses. lucene 2.1 uses it as default for the range querys in the queryparser. in 2.0 you can use it programing yourself the query clause, or modifying the queryparser to use it instead the default rangequery.
You should also take care of the float numbers, because the alfanumeric characteristic of the order, -1 < -2 . NumberUtils in Solr is a class for obtain a float representation that can be sortable in alfanumeric order. You can take a look to it for better understand. Jokin On 3/22/07, rzr rzr <[EMAIL PROTECTED]> wrote:
Hi, I've got a couple of questions. I'm posting them in two seperate mails to keep the subject headers relevant. Given: Relatively large databases that contain many records. Each database consists of a large file which may contain as much as 2M records. Each record consists of several fields, though exaclty what fields and how many of them may vary. The records are seperated by a NewLine/Cr/CrLf combination. The database contains GPS ranges. These ranges describe a small, rectengular slice of the earth. The numeric ranges are in a fixed field. Question: Using lucene .net, would it be possible to do a numeric comparison to test whether a %QueryValue% is smaller than, equal to or larger than the value in a all/any indexed GPS fields?
