query_for_record fails with single_index in r143.

simple-minded patch -not tested to be free of side-effects.

right, it's pointless to store the class name in aaf_configuration with a shared index. I'll fix this soon.

fixed

I am still seeing failures with single_index when deleting records -the same high-level symptom I was seeing before when the cause was as documented on this ticket.

I have single_index configured for AR models Medium, Portfolio, Place and Person. Here is an excerpt from my Unit test that fails:

require File.dirname(__FILE__) + '/../test_helper'
require 'uuidtools'

class ActiveRecordTest < Test::Unit::TestCase
  fixtures :users, :places, :people, :media, :portfolios, :placements, :medium_portfolios, :authorizations

  def setup
    index = Medium.aaf_index.ferret_index
    index.size.times {|i| index.delete(i)}
    Medium.rebuild_index(Person, Place, Portfolio)
  end
  
  def test_search_after_delete
    results = Medium.find_id_by_contents("Collection", {:models => :all})
    assert_equal 2, results.first
    Portfolio.destroy(portfolios(:myCollection))
    results = Medium.find_id_by_contents("Collection", {:models => :all})
    assert_equal 1, results.first
  end
end

My setup just rebuilds the index from scratch -I know of no better way to run tests on the functionality of AAF. Note that I start with TWO fixtures with the word "Collection" in them. The first assertion is true -no problem. One of the two matching fixtures is portfolios(:myCollectio), which is then deleted. Unfortunately, the second assertion fails with "1 expected, but was 2".

Note that I have some other AAF related tests (adds, simple AR updates) and they all work fine.

-Chris

now really fixed, thanks for the test case.