Wolf,

Updating works.  Thanks for the help!

- Steve

On Oct 8, 10:01 am, Steve Eichert <[EMAIL PROTECTED]> wrote:
> Ok, I'll try updating and see if that helps.
>
> On Oct 8, 2:29 am, Wolf <[EMAIL PROTECTED]> wrote:
>
> > You need to update TS.
>
> > "sql_query_range  = SELECT MIN(`id` * 3 + 0), MAX(`id` * 3 + 0)" is an
> > outdated and wrong statement.
>
> > regards,
> > Wolf
>
> > On 7 Okt., 22:54, Steve Eichert <[EMAIL PROTECTED]> wrote:
>
> > > It returns all the records when I strip off the id range portion of
> > > the query.  I don't see anything out of the ordinary in the SQL.  Any
> > > ideas for further investigation?
>
> > > sql_query_pre    = SET NAMES utf8
>
> > > sql_query_pre    =
> > > sql_query        = SELECT `territories`.`id` * 3 + 2 AS `id` ,
> > > CAST(`territories`.`name` AS CHAR) AS `name`,
> > > CAST(`territories`.`number` AS CHAR) AS `number`, `territories`.`id`
> > > AS `sphinx_internal_id`, 1803926469 AS `class_crc`, '1803926469' AS
> > > `subclass_crcs`, 0 AS `sphinx_deleted` FROM territories    WHERE
> > > `territories`.`id` * 3 + 2 >= $start   AND `territories`.`id` * 3 + 2
> > > <= $end    GROUP BY `territories`.`id`  ORDER BY NULL
> > > sql_query_range  = SELECT MIN(`id` * 3 + 0), MAX(`id` * 3 + 0) FROM
> > > `territories`
> > > sql_query_info   = SELECT * FROM `territories` WHERE  `id` = (($id -
> > > 2) / 3)
> > > sql_attr_uint        = sphinx_internal_id
> > >   sql_attr_uint        = class_crc
> > >   sql_attr_uint        = subclass_crcs
> > >   sql_attr_uint        = sphinx_deleted
>
> > > }
>
> > > index territory_core
> > > {
> > > source = territory_0_core
> > > path = /path/to/territory_core
> > > charset_type = utf-8
> > >   morphology     = stem_en
> > >   enable_star    = 1
> > >   min_prefix_len = 1}
>
> > > index territory
> > > {
> > >   type = distributed
> > >   local = territory_core
> > >   charset_type = utf-8
>
> > > }
>
> > > On Sep 18, 2:49 am, Pat Allan <[EMAIL PROTECTED]> wrote:
>
> > > > Yeah, looking at the sql_query for the source in question is where I'd  
> > > > start. If you strip off the id range part of the WHERE clause, how  
> > > > many records does it return?
>
> > > > Cheers
>
> > > > --
> > > > Pat
>
> > > > On 18/09/2008, at 10:17 AM, Blake Watters wrote:
>
> > > > > Try examining the SQL generated in your sphinx.conf file for the  
> > > > > index in question. It may have insight.
>
> > > > > On Wed, Sep 17, 2008 at 5:03 PM, Steve Eichert <[EMAIL PROTECTED]
> > > > > > wrote:
>
> > > > > When running rake ts:in ThinkingSphinx is excluding a row form the
> > > > > index that is created.  I have 68 rows in the database and when
> > > > > indexing it says "collected 67 docs".  My index doesn't have any
> > > > > filters:
>
> > > > > class Territory < ActiveRecord::Base
> > > > >  #...
>
> > > > >  define_index do
> > > > >    indexes :name, number
> > > > >  end
>
> > > > >  #...
> > > > > end
>
> > > > > What would cause TS to exclude a row from the index it creates?  From
> > > > > evaluating the data in the table there doesn't appear to be anything
> > > > > unique to the excluded row.  Below is the migration for the table that
> > > > > is having a row excluded.
>
> > > > >    create_table :territories do |t|
> > > > >      t.integer :study_id, :null => false
> > > > >      t.string :name, :null => false
> > > > >      t.string :number, :null => false
> > > > >      t.string :region_name, :null => false
> > > > >      t.string :region_number, :null => false
> > > > >      t.string :district_name, :null => false
> > > > >      t.string :district_number, :null => false
>
> > > > >      t.timestamps
> > > > >    end
>
> > > > > Any ideas?
>
> > > > > Thanks,
> > > > > Steve
--~--~---------~--~----~------------~-------~--~----~
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