I'm probably confusing myself, but I'll try to explain...

I ran into this issue when trying to use sphinx with my cucumber
feature (tests). I've decided to enable TS for my cucumber tests by
specifying:

ThinkingSphinx.updates_enabled = true
ThinkingSphinx.deltas_enabled = true

in my features/steps/env.rb file.

I also have the following in my config/sphinx.yml:

development:
  port: 3312

test:
  port: 3313

So basically I run two indexers at once when I'm working
(RAILS_ENV=development rake ts:start && RAILS_ENV=test rake ts:start).

I find that when I use the HEAD of the master branch
(b9e4294028a541fc58f6a5829db70be30b85fa19 as of this message) I get
the array of nil problem:

class Context < AR::Base
  # ...
  define_index do
    indexes :name, :sortable => true
    indexes :desc

    has state_status, created_at
    set_property :delta => true
  end
  # ...
end

> Factory.create(:context, :name => 'context 1')
> Factory.create(:context, :name => 'context 2')
> Factory.create(:context, :name => 'context 3')

...

using config file '/Users/agib/Sites/site/config/test.sphinx.conf'...
indexing index 'context_delta'...
collected 1 docs, 0.0 MB
sorted 0.0 Mhits, 100.0% done
total 1 docs, 27 bytes
total 0.015 sec, 1793.07 bytes/sec, 66.41 docs/sec
rotating indices: succesfully sent SIGHUP to searchd (pid=3572).
Sphinx 0.9.8.1-release (r1533)
Copyright (c) 2001-2008, Andrew Aksyonoff

...

> Context.search 'context'

=> [nil, nil, nil]

I switched back to 3e5fc7370b93e543ffd6ca2e0f240bec47baf4b9 and no
longer have the problem... has anyone else had similar issues?

Thanks in advance for any help!

Best,
Aaron
--~--~---------~--~----~------------~-------~--~----~
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