Hi James There's no performance difference between the two methods - but #for translates strings to their integer values and redirects field facets to their *_facet attributes. If you're dealing with normal attribute values, then you should be able to use either.
Thanks for those docs, too :) -- Pat On 23/07/2009, at 5:54 PM, James Earl wrote: > > Hey Pat, > > Does it matter performance-wise if a selected facet is passed into > ThinkingSphinx::Search.search vs. > ThinkingSphinx::FacetCollection.for? It would seem if someone didn't > mind having their facets filtered, then it would be more convenient to > just bypass the facets.for step. > > On a separate note, I'd be happy to help with the faceting > documentation once I feel like I understand what I'm doing :) > > James > > On Jul 23, 7:42 am, Pat Allan <[email protected]> wrote: >> Hi James >> >> Yup, was definitely intentional - don't want to hammer the Sphinx >> daemon any more than necessary. >> >> -- >> Pat >> >> On 22/07/2009, at 11:25 PM, James Earl wrote: >> >> >> >>> Was the facet api design intentional, in how facets are retrieved >>> separate from the search results? I like that it allows you to >>> narrow >>> your search while not narrowing the list of facets. :) >> >> > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
