If memory serves me correctly (I have not done this for a good while), you can specify the file types to include (and exclude) in the indexing. Another trick would be to move the queries to stored procedures thereby eliminating this particular problem. From: "Dave Shuck" <[EMAIL PROTECTED]> Date: 2002/10/10 Thu AM 09:45:30 CDT To: <[EMAIL PROTECTED]> Subject: Verity question
I have set up a Verity collection to search for content in all files in recursive directories under a web root. Obviously when including CF files in the list of files to search, you end up with any matching string even if it appears in CF code. What is the best approach to avoid this? For instance, I am working on a site that sells roofing materials. If I do a search for 'shingle', and I have a query that consists or "SELECT [something] FROM tblShingle", it will return that page and the "summary" value will display CF code. Obviously that is not cool. Any thoughts on the best way to tackle that? tia ~Dave ------------------------------------------------------------------------- This email server is running an evaluation copy of the MailShield anti- spam software. Please contact your email administrator if you have any questions about this message. MailShield product info: www.mailshield.com ----------------------------------------------- To post, send email to [EMAIL PROTECTED] To subscribe / unsubscribe: http://www.dfwcfug.org ------------------------------------------------------------------------- This email server is running an evaluation copy of the MailShield anti- spam software. Please contact your email administrator if you have any questions about this message. MailShield product info: www.mailshield.com ----------------------------------------------- To post, send email to [EMAIL PROTECTED] To subscribe / unsubscribe: http://www.dfwcfug.org
