Hi! On Mon, Oct 16, 2006 at 04:23:28PM +0900, David Balmain wrote: > On 10/16/06, Charlie Hubbard <[EMAIL PROTECTED]> wrote: [..] > > I'm interested in your database approach. It could help simplify this > > problem. It seems doable to add this to acts_as_ferret without needing > > a seperate project. Not to mention it's really needed in Rails apps as > > well. > > > > In my suggested database approach the search would be the equivalent > of a simple SQL join query. By adding a feature like this to > acts_as_ferret you'll need to pull all the matching page ids out of > the index and peform a much slower SQL query for all books that > include those page ids. I'm not sure it is feasible but I'll leave > that decision to the acts_as_ferret developers. The best solution is > definitely to index all the pages with the book document, even if it > means indexing each page twice.
I'd suggest going that route, too. An imho interesting question around this is, how much the size of the value for that pages field containing all pages of a book really would influence the total index size (when not storing the contents and not storing term vectors), i.e. will the index size grow in a linear way, or will it grow slower over time, as with bigger size of the value of a field more terms occur more than once ? Jens -- webit! Gesellschaft für neue Medien mbH www.webit.de Dipl.-Wirtschaftsingenieur Jens Krämer [EMAIL PROTECTED] Schnorrstraße 76 Tel +49 351 46766 0 D-01069 Dresden Fax +49 351 46766 66 _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
