On Wed, Jan 21, 2009 at 9:55 AM, Ard Schrijvers <[email protected]> wrote: > But, I can never tell when I see '@someprop < 5' whether the 5 should be > interpreted as a string, as a double or a long.
Once the query implementation comes to comparing someprop to "5", it could try to convert 5 to the type of the property, eg. from long to double, before doing the conversion. This is what the spec suggests (but only saying "can"). I can imagine this is difficult because that step is passed on to the lucene index lookup which requires the exact same data type; if this is the case, one might think about storing both double and long properties in the lucene docs as double and always convert the literal from the query to double... although one might loose some of the higher long values in that case. Regards, Alex -- Alexander Klimetschek [email protected]
