On Sat, Dec 09, 2006 at 08:49:36AM +0100, Mark wrote:
> Sam,
>
> > If you're making your own QueryParser, there is another gotcha -> the
> > docs say to use the parameter handle_parser_errors but that's not right
> > with 0.10.13. It should be
> >
> > Ferret::QueryParser.new({:handle_parse_errors => true}) # not
> > handle_parser_errors like docs say
> >
> > Note the missing r on parse(r)
>
> acts_as_ferret( { :fields => { 'ferret_index_article_title' => {
> :boost => 2 },
> 'ferret_index_article_body' => { :boost
> => 1.5 },
> 'ferret_index_article_comments' => {
> :boost => 1 },
> 'ferret_index_article_image_captions'
> => { :boost => 1.5 } }, :store_class_name => true },
> { :analyzer =>
> Ferret::Analysis::StandardAnalyzer.new([nil])} )
>
> I'm not specifically creating my own QueryParser object. Any idea where
> i would stick the :handle_parse_errors => true in the above.
right after your :analyzer option into the second options hash:
aaf( { :fields => { ... }, :store_class_name => true },
{ :analyzer => ..., :handle_parse_errors => true } )
aaf however doesn't create it's own query parser for normal use cases,
but the option will be given to the internal Ferret Index instance, so
maybe it helps anyway. please tell me if it does so I can correct the
default parameter name in aaf.
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
