Hi Wotjek To be honest, I'm not sure what the answer is here… I initially thought attributes would perform better (as you're avoiding the Sphinx query parser and any complications with morphologies and character encodings and so on), but others more familiar with the underlying code in Sphinx have suggested I'm wrong. I've not done any tests, but if performance is key, you should probably compare the two in a situation that matches your requirements.
Would definitely be interested in hearing what you find works best. Cheers -- Pat On 07/12/2011, at 6:00 PM, Wojciech Mach wrote: > Hi, say I am building a job search page, each job has a country and one or > more languages. > I don't expect countries and languages data to change much, I'm fine keeping > objects in memory all the time (railscast #189 embedded association, I wrote > a similar gem for it https://github.com/wojtekmach/embedded_record). > Question is what would be better sphinx performance wise. Have habtm > association and stick to thinking-sphinx indexing language_ids, or have > language_ids string column with list of ids, set :type => :multi and use > plugin like embedded_record. As fair I know sphinx can't index bitmask column > but can string list of integers. > > Cheers, > Wojtek > > -- > 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. -- 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.
