Problem with Single Table Inheritance models about searchkick HOT 4 CLOSED

Thanks for reporting! I'll fix it this weekend.

from searchkick.

Looks like the fix is more involved than I thought karmi/retire#178

Here's one way to do it:

class Dog < Animal
end

Animal.reindex # creates an index animals_development
Dog.reindex    # creates an index dogs_development

Animal.search  # searches animals_development
Dog.search     # searches dogs_development

dog = Dog.first
dog.save       # saves changes in both indexes if both exist

Another possibly simpler way would be:

Animal.reindex # creates an index animals_development
Dog.reindex    # creates an index animals_development

Animal.search  # searches animals_development
Dog.search     # searches animals_development for _type dog

dog = Dog.first
dog.save       # saves changes in one index

I'll have to think more about this. Let me know your thoughts.

from searchkick.

Personally, I think the second solution would work fine. It feels like how I would expect it to work.

Jens Ljungblad

On Sunday 8 September 2013 at 17:37, Andrew Kane wrote:

Looks like the fix is more involved than I thought karmi/retire#178 (karmi/retire#178)
Here's one way to do it:
class Dog < Animal end Animal.reindex # creates an index animals_development Dog.reindex # creates an index dogs_development Animal.search # searches animals_development Dog.search # searches dogs_development dog = Dog.first dog.save # saves changes in both indexes if both exist

Another possibly simpler way would be:
Animal.reindex # creates an index animals_development Dog.reindex # creates an index animals_development Animal.search # searches animals_development Dog.search # searches animals_development for _type dog dog = Dog.first dog.save # saves changes in one index

I'll have to think more about this. Let me know your thoughts.

—
Reply to this email directly or view it on GitHub (#30 (comment)).

from searchkick.

Yeah, the second solution made the most sense. Give it a shot!

from searchkick.