Re: [htdig3-dev] Re: Multiple database (patch)


Subject: Re: [htdig3-dev] Re: Multiple database (patch)
From: Rajendra Inamdar (inamdar@beasys.com)
Date: Wed Feb 09 2000 - 13:03:20 PST


Rajendra Inamdar wrote:

> >
> > > If a search policy is selected by the user, it is used as the
> > > search_algorithm for the search session.
> > [snip]
> >
> > I'm not quite sure how this is any different from setting:
> > allow_in_form: search_algorithm
> >
> > Then you make a pop-up in the search output for the appropriate
> > algorithms. Or you could use the new build_select_list to make the pop-up.
> > It seems like it's already in there...
> >
> > -Geoff
> >
>
> You are right. I guess I did not notice the allow_in_form. The code for
> search_policies is quite localized, so it can be easily stripped out. In
> any case, it has nothing to do with multiple databases.
>
> Incidently, when I moved to 3.2.x, my searches using "substring" algorithm
> seem to be running slower than with 3.1.3. Has anybody had similar
> experience?
>
> /Raj
>

One of the motivations behind the search_policies attribute was to make
the user selection persistent over multiple search sessions. If the selection
is not persistent, it is very likely that the user may not notice that something

changed. It is not clear if "allow_in_form" can be used to achieve similar
effect.

/Raj

------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
htdig3-dev-unsubscribe@htdig.org
You will receive a message to confirm this.



This archive was generated by hypermail 2b28 : Wed Feb 09 2000 - 12:59:51 PST