I have been using Thinking Sphinx for a while in a production application and have nothing but great things to say.
Recently my customers have been asking to add the extended match mode functionality so that they could search with '@foo bar' type of syntax. >From the looks of it I just add :match_mode => :extended to my search call and it is done. I've tested it a bit and it seems that regular searching still works the same way as it does in default :any match mode. Should I be concerned or aware of any major differences between :any and :extended match modes that might negatively impact my customers (performance, errors, etc.)? Or do I basically get :any with addition of ability to use the extended syntax by setting match mode to :extended? I am just a little nervous about simply changing this setting and moving it to production, but I have not been able to find any disadvantages. Thanks in advance for the input. -- 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.
