Hi Curtis,
I have done this on the front-end with decent results, using the
"exclude" and "include" variables against one all-inclusive database.
Since databases (configs) usually differ by the servernames and/or paths
htdig was pointed to, it seems this would usually work.
Curtis Ireland wrote:
>
> Here is an idea for future releases. I'm not exactly sure how you would
> do this, but then you are the programmers for this package :)
>
> In my current set-up, I have about six different databases plus one
> all-inclusive. What I would eventually like to do is allow the visitor
> to select two or more search databases to search through.
>
> To achieve this in the current set-up, I would have to merge my tables
> together in every possible combination.
> -C
>
> --
> Curtis Ireland - [EMAIL PROTECTED]
> Solidum Systems - http://www.solidum.com
> (T) (613)724-6004 x284 - (F) (613)724-6008
>
> ------------------------------------
> To unsubscribe from the htdig3-dev mailing list, send a message to
> [EMAIL PROTECTED]
> You will receive a message to confirm this.
--
Erik Lyons <[EMAIL PROTECTED]>
webmaster, GemStone Systems, a Brokat Company
(503) 533-3670 http://www.gemstone.com
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
