On Tue, May 08, 2007 at 11:35:48AM +0200, Jens Kraemer wrote:
[..]
> > acts_as_ferret({:fields => {:name => {:boost => 10},
> > :type => {:boost => 2},
> > :email => {:boost => 10},
> > :bio => {:store => :no},
> > :status_id => {:boost => 1}},
> > :store_class_name => true,
> > :remote => true,
> > :ferret => { :analyzer =>
> > Ferret::Analysis::StandardAnalyzer.new([]) }
> > } )
> >
I just committed a fix so that the above call should be working
correctly now. I'd go so far to say that this should be the preferred
way of passing ferret options to aaf now. The two-hash calling style I
suggested below will still work of course, so nothing should break.
Thoughts anyone?
Old calling style:
>
> acts_as_ferret({ :fields => {:name => {:boost => 10},
> :type => {:boost => 2},
> :email => {:boost => 10},
> :bio => {:store => :no},
> :status_id => {:boost => 1}},
> :store_class_name => true,
> :remote => true
> }, {
> :analyzer => Ferret::Analysis::StandardAnalyzer.new([])
> })
>
> Please note the difference: the analyzer option is part of a second
> options hash.
>
--
Jens Krämer
webit! Gesellschaft für neue Medien mbH
Schnorrstraße 76 | 01069 Dresden
Telefon +49 351 46766-0 | Telefax +49 351 46766-66
[EMAIL PROTECTED] | www.webit.de
Amtsgericht Dresden | HRB 15422
GF Sven Haubold, Hagen Malessa
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk
