It's because you're referencing associations in your index definition - and so the SQL that gets generated has joins to other tables. This is why there's more than one searchable column available.
Cheers -- Pat On 22/01/2011, at 6:24 PM, Z@M wrote: > Thanks Pat . it worked . > But i wonder why that namespace problem happens . > we dont need to specify the table name if we are dealing only with one > table rt ? > select * from users = select users.* from users > > is sphinx combining the conditions and building a unique query for > indexing ? > > On Jan 22, 6:34 am, Pat Allan <[email protected]> wrote: >> The issue here is that you're referring to searchable without clarifying >> which table you want it from. Try changing the 'where' call to the following: >> >> where "users.searchable = true" >> >> -- >> Pat >> >> On 22/01/2011, at 12:42 AM, Z@M wrote: >> >>> define_index do >> >>> where "searchable = true" >>> indexes only_admin, :as => :only_admin >> >>> indexes first_name, middle_name, last_name >> >>> indexes preferences.name, :as => :preferences_name >>> indexes preferences.value, :as => :preferences_value >> >>> indexes current_contact.location.country.name, :as >>> => :current_country, :facet => true >>> indexes current_contact.location.state.name, :as >>> => :current_state, :facet => true >>> indexes current_contact.location.city.name, :as >>> => :current_city, :facet => true >> >>> set_property :delta => :delayed >> >>> end >> >>> I have other models which i am indexing . all of them have search-able >>> column in their table. >>> Will that create a problem here ? >> >>> I still having the mysql error . >>> Mysql is taking 100% memory when i do rake ts:rebuild >>> also when i save the user model from console. >>> it eats up the /tmp memory and the system shows warning and ask for >>> disk cleanup >>> i am really worried about this behavior. >> >>> On Jan 21, 4:54 am, Pat Allan <[email protected]> wrote: >>>> What does your index definition look like for your user model? >> >>>> And I'm guessing you got the other issue (for MySQL) fixed, since it's no >>>> longer happening when you're indexing? >> >>>> -- >>>> Pat >> >>>> On 20/01/2011, at 10:42 PM, Z@M wrote: >> >>>>> indexing index 'users_core'... >>>>> ERROR: index 'users_core': sql_range_query: Column 'searchable' in >>>>> where clause is ambiguous (DSN=mysql://root:***@localhost:3306/ >>>>> myname). >> >>>>> cant i use the searchable keyword . is it reserved ? >> >>>>> -- >>>>> 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 >>>>> athttp://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 >>> athttp://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. > -- 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.
