Hmm, what's the sql_query that's generated for track_core? The error  
from Sphinx might be misleading with the reference to field list.

-- 
Pat

On 13/12/2008, at 11:24 PM, j0llyr0g3r wrote:

>
> Hey guys,
>
> i get the following error message when running "rake
> thinking_sphinx:index"
>
>
> CODE:
> indexing index 'track_core'...
> ERROR: index 'track_core': sql_range_query: Unknown column
> 'tracks.beat' in 'field list' (DSN=mysql://yourtunes:*...@localhost:
> 3306/yourtunes_development).
>
> My migration (only the relevant parts) looks like this:
>
> CODE:
> class CreateTracks < ActiveRecord::Migration
>  def self.up
>    create_table :tracks do |t|
>      t.string :artist
>      t.string :title
>      ...........
>      t.integer :track_length
>      ...........
>      t.boolean :loop, :default => false
>      t.boolean :beat, :default => false
>      t.boolean :vocals, :default => false
>    end
>  end
>
> And here is the "define index" part from the model:
>
> CODE:
>  define_index do
>    # enable keyword search 'tags', 'artist','title',
> 'short_description', 'full_description'
>    indexes tags, :sortable => true
>    indexes short_description, :sortable => true
>    indexes full_description, :sortable => true
>    indexes artist, :sortable => true
>    indexes title, :sortable => true
>    attribute beat
>    attribute vocals
>    # we _must_ use a symbol here, because loop is also a ruby kernel
> method
>    attribute :loop
>    has track_length
>  end
>
> Now, what i don't get is:
>
> Why does sphinx / thinking sphinx want to index an attribute?
>
> How can i solve this problem?
> >


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