Technically, Sphinx only supports integer MVA's, so removing :multi from translate should do the job. Consider it committed :)
Lee: I'm keeping an eye on your branch, will look over your commits when I have some time. And generally, thanks all for your patience with this. The facets code is pretty volatile at the moment, with all these patches and my own work on it, so it's a bit hard to get many patches in right now. Having the input is really helpful though, to get my head around the ways people need facets to work. Cheers -- Pat On 19/02/2009, at 7:45 AM, Lee Iverson wrote: > > Dan Pickett wrote: >> I think this is probably due to the send call in translate of >> facet.rb >> - I proposed and am still considering creating a translation field >> for >> crc'd attributes like dates and strings in the generated >> configuration. The indexed fields wouldn't be a problem because >> they're already in the query. >> > Well, for :multi facets with integer values, the attribute_value in > Facet#value is the correct one, so there should be no need to call > translate (in fact, simply removing :multi from the "when :string, > :multi" line in Facet#value does the right thing. I'd suggest > prohibiting non-integer multi value facets on the front-end and then > just making this small change to Facet#value on the back-end, > otherwise > we're left with the problem of trying to figure out which of the array > of values to follow to the end in Facet#translate. > > I'm working on this in my branch at > http://github.com/leei/thinking-sphinx/tree/master > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
