Hi Ryan

This might be tied to the English language stemmer, which Thinking  
Sphinx uses by default. Have a look at this old thread for a way to  
disable english as the default morphology:
http://groups.google.com/group/thinking-sphinx/browse_thread/thread/3aca8ba301543765

Cheers

-- 
Pat

On 21/03/2009, at 11:00 AM, Ryan Bigg wrote:

>
> When I go to search in script/console I can do it as a find_by_name:
>
> Loading production environment (Rails 2.2.2)
>>> Customer.find_by_name("Trogdor")
> => #<Customer id: 2761, name: "trogdor", priority_id: nil, delta:
> false, comments: nil, old_id: nil, old_mailing_address: nil,
> phone_number: nil>
>
> But not a search:
>
>>> Customer.search("Trogdor")
>
> Even though my model has:
>
> define_index do
>   indexes :name
>   set_property :delta => true
> end
>
> It was suggested to me that I try using the search command instead:
>
> search -c config/production.sphinx.conf Trogdor
> Sphinx 0.9.8.1-release (r1533)
> Copyright (c) 2001-2008, Andrew Aksyonoff
>
> using config file 'config/production.sphinx.conf'...
> index 'history_core': search error: failed to open /var/www/select-
> copiers/releases/20090315221508/db/sphinx/production/history_core.sph:
> No such file or directory.
>
> So that didn't work.
>
> When I run rake ts:config; rake ts:in it generates files in db/sphinx/
> production like this: history_core.new.sph, rather than
> history_core.sph.
> Could this be the source of my issue?
>
> Even *after* running rake ts:in, Trogdor is nowhere to be found.
> My only thoughts are he is burninating the countryside somewhere.
>
> -----
> Ryan Bigg
>
>
>
>
>
>
>
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to