On Mon, Oct 02, 2006 at 12:03:31PM +0200, David Wennergren wrote: > > please note that this will only work with :limit => :all, otherwise > > you'll only sort the subset of records retrieved from ferret, not the > > whole result set. > > Just to make sure that I don't misunderstand something. If I skip the > find_options but use a Ferret sort field I get the correct result (for > exampel, 20 hits ordered by name). > > My problem was that if I didn't provide the find_options, the records > when loaded with an sql like this (in the find_by_contents method) > "items.id in (1,12,13,45,23)" was still in the wrong order unless a > passed an find_options ordering them by "name".
aaf is supposed to retain the sorting of results delivered by Ferret. The records retrieved with the sql 'in' clause are sorted afterwards so they are in the same order as the originial Ferret result set. At least that is how it is supposed to be. Could you please post your acts_as_ferret declaration, and the snippet where you call find_by_contents, so I can check if this is a bug in aaf? cheers, 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
