Hi John I've not hit that before - but filtering (or indexing) strings when they're meant to be floats wouldn't be ideal at all. Are you storing the floats as a field or an attribute? If the former, I guess Sphinx's word-splitting would take . as a delimiter, hence why 7 would match as well.
Cheers -- Pat On 10/12/2008, at 6:42 AM, brez wrote: > > Ran across an issue with Sphinx with filters and float values (or > floats stored as strings) - not related to Thinking Sphinx but a > problem with Sphinx (confirmed by using the search client directly) - > anyhow something is truncating floats so if you do a search with a > filter of '7.5' it'll match both 7.5 and 7 - didnt have any time to > track down any Sphinx bugs so just extended the values (like is > commonly done for currency) to '70' and '75' to fix in the meantime - > anybody else run across this? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/thinking-sphinx?hl=en -~----------~----~----~----~------~----~------~--~---
