Well, maybe I am missing something but here is what I think is going on. search is made and if searchScope is News (lets assume that) , then you are searching in collection. If results are found, then you are doing a cfquery and returning resultset from db. Perhaps that logic is not true. Ideally, when you search a collection, it returns result columns (just like google search), few lines of text & summary. So after search you should show those columns ( and not straight query, which defeats purpose of collection) which are #context# and #summary# returned by cfsearch.
Bottomline, results should be shown which are returned from a. collection or b. use columns returned by collection to query the db, like for example select * from tbl where col1 like 'collectionname.context' Hope this helps. Also have a look at cfsearch in cfdocs. <Ajas Mohammed /> http://ajashadi.blogspot.com We cannot become what we need to be, remaining what we are. No matter what, find a way. Because thats what winners do. You can't improve what you don't measure. Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives. On Thu, Jul 30, 2009 at 1:50 PM, Jeff Howard <[email protected]> wrote: > Not using Verity is not really an option in this situation. This is an > existing application that I am trying to debug for a client. The code has > all be written and they asked me if I could figure out why they are getting > the same results regardless of keyword for their "news" search. Looking > through the code, it works for the other 3 searches, it just doesn't seem to > be working for one of the searches. > > Here is the code: > > <!--- Search news for keywords ---> > <CFIF Len(Trim(Keywords)) AND (form.SearchScope IS "All" OR > form.SearchScope IS "News")> > <CFSEARCH NAME="NewsSearch" > COLLECTION="NCEF_News" > MAXROWS="#MAXROWS#" > CRITERIA="#LCase(Keywords)#"> > <CFIF NewsSearch.RecordCount> > <!--- Query Calendar Database ---> > <CFQUERY NAME="session.GetNewsData" DATASOURCE="#DSN#" BLOCKFACTOR="10" > CACHEDWITHIN="#CreateTimeSpan(0, 0, 15, 0)#"> > SELECT * > FROM News > WHERE NEWS_STATUS='approved' > AND NEWS_Archive=0 > ORDER BY NEWS_DATE desc > </CFQUERY> > <CFSET GetNewsData = True> > <CFELSE> > <CFSET GetNewsData = False> > </CFIF> > <CFELSE> > <CFSET GetNewsData = False> > </CFIF> > > > On Thu, Jul 30, 2009 at 1:35 PM, John Mason <[email protected]> wrote: > >> Don't use verity unless you have to control the output in a very >> particular way. It's a dying engine and probably will not be with us much >> longer. Google has custom search engine technology that will work for most >> of your needs. Thankfully, Adobe will finally put Lucene in CF9 - several of >> us have been asking for some time now. >> >> John >> [email protected] >> >> >> >> >> >> Jeff Howard wrote: >> >>> Hello all. >>> I have not had to use verity to much in my application development and >>> am currently trying to troubleshoot errors in search results for an existing >>> application. I am reading over the documentation on Adobe site now but I >>> thought it might be helpful to hit the group up for any tips. >>> The issue I am currently trying to troubleshoot is that one of the >>> collections is returning the same number of results for all search terms, >>> i.e. regardless of search term all records are returned. >>> Is this an indexing issue? >>> Are there any standard basic first steps to debugging search issues? If >>> so, what? >>> Are there any other tips or pointers to keep in mind when working with >>> Verity? >>> >> >> >> >> ------------------------------------------------------------- >> >> To unsubscribe from this list, manage your profile @ >> http://www.acfug.org?fa=login.edituserform<http://www.acfug.org/?fa=login.edituserform> >> >> For more info, see http://www.acfug.org/mailinglists >> Archive @ http://www.mail-archive.com/discussion%40acfug.org/ >> List hosted by http://www.fusionlink.com >> ------------------------------------------------------------- >> >> >> >> >
