|
I've been trying to implement acts_as_ferret in my
latest project and ran into a snag. If I do a search for 'auditor state' then
the search works perfectly. If I include a stop word, as in 'auditor of state',
then I get no results. I'd prefer not to set stop
words to nil and index everything.
The solution, that I have yet to attempt, is to use
Ferret::QueryParser instead of passing the query as a string to the search
method.
I couldn't find a way to do this with the current acts_as_ferret plugin and was wondering if modifying the plugin to have a "ferret_query_parser" method would be better than trying to use Ferret directly from my app model. Also, wouldn't this approach be necessary if I implement my own analyzer? I
was thinking of possibly using the double metaphone algorithm and thinking that
without the query parser to analyze the search string using my custom analyzer
that I wouldn't get any results.
I hope that I haven't missed something obvious in aaf's api.
On a side note, is there any recommended place to place custom analyzers
for rails apps?
Thanks,
Curtis
|
_______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
