According to Jerry Asher:
> It appears I can get htDig to loop across multiple config files (and
> databases) by specifying multiple config parameters on the command line.
>
> So what is the difference between specify multiple config parameters and
> specifying a collection_names parameter? Will one result in a faster
> search than the other?
There's a world of difference between these. The documentation for the
collection_names attribute is misleading. All this attribute does is
define a list of possible "config" values for the follow-up search form,
and is used to generate a series of template variables for this purpose.
It has no bearing whatsoever on the config files that will be used in the
current search. The collection_names attribute is largely obsolete now,
as you can do essentially the same thing in a cleaner way with the newer
build_select_lists attribute.
When the patch for collections was first contributed, it came with several
files which showed an example of its usage. Those files never made it
into the source distribution, and seem to be lost now. You mind find
them somewhere in the mail archives from about a year and a half ago.
They were contributed by Rajendra Inamdar <[EMAIL PROTECTED]>, as
indicated in the ChangeLog file. I don't have time to hunt them down
just now.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
