> Why don't you just index the email address right along with the Person? > Do you ever need to find a single EmailAddress object? If not, just > don't index them in their own index. Instead add a custom field to > Person's acts_as_ferred statement for the email address value.
I would index the email address right along with the person, but there is a multiple association there. I would have to index a whole lot of other data that I would like to be able to search through: has_many :phone_numbers has_many :addresses has_many :email_addresses has_many :enrollments has_many :facilities_applications has_many :course_invoices has_many :refunds has_many :medications has_many :instructor_bios has_one :immunization has_one :administrator put that with the fact that I have over 50 models ( all with many associations ) in my application of which at least half of need to be searchable, and that turns into a large task. I created a module that helps me generate functions for list views ( with sorting and searching ) that used mysql fulltext searching, but when searching through ~100,000 records, it would take the app upwards of 7 seconds to finish finding results. So I was rewriting it to work with acts_as_ferret. So I would assume that acts_as_ferret multi_search doesn't have the ability to be told that I only want one type of model even though i want to search through multiple models (to get associations). -- Posted via http://www.ruby-forum.com/. _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
