That is quite a good approach, but we have to actually perform that extra
step in order to get what we want. Of course, I think it would be better if
Verity can take care of everything so that we don't even have to use SQL to
search and filter out the necessary records..
roger
----- Original Message -----
From: "Seth Petry-Johnson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 17, 2000 9:55 PM
Subject: Re: Understanding verity search...
> > You could use Verity to search the text fields.
> > But all you want from Verity is a list of record
> > IDs of those records that match your Text Field(s)
> > Search Criteria, I'll call it "VerityQuery.ID"
> >
> > Then you could use SQL to search on the Non-Text
> > Field(s) of only the records that match your Verity
> > search results:
>
> Duh... I guess that is a better approach then looping over the Verity
> results and manually filtering each record. I guess that's why you
> shouldn't write code for 12 hours straight. You begin doing some stupid
> things <g>.
>
> If I use the MAXROWS parameter to cap the Verity results at a reasonable
> number then there really shouldn't be too much of a performance problem...
>
> Thanks for the idea,
> Seth
>
> --------------------------------------------------------------------------
----
> Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
> To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
