Can I use ht://Dig to index and search an SQL database?
You can if your database has a web-based front end that can be “spidered” by ht://Dig. The requirement is that every search result must resolve to a unique URL which can be accessed via HTTP. The htdig program uses these URLs, which you feed it via the start_url attribute, to fetch and index each page of information. The search results will then give a list of URLs for all pages that match the search terms. If you don’t have such a front end to your database, or the search results must be given as something other than URLs, then ht://Dig is probably not the best way of dealing with this problem: you may be better off using an SQL query engine that works directly on your own database, rather than building a separate ht://Dig database for searching.
You can if your database has a web-based front end that can be “spidered” by ht://Dig. The requirement is that every search result must resolve to a unique URL which can be accessed via HTTP. The htdig program uses these URLs, which you feed it via the start_url attribute, to fetch and index each page of information. The search results will then give a list of URLs for all pages that match the search terms. If you don’t have such a front end to your database, or the search results must be given as something other than URLs, then ht://Dig is probably not the best way of dealing with this problem: you may be better off using an SQL query engine that works directly on your own database, rather than building a separate ht://Dig database for searching. Ted Stresen-Reuter had the following tips: “In my case, because I like htdig’s ability to rank results (and that ranking can be modified), I created an index page that simply walks through each record and indexes each record (with next and pr
