> Thanks to Dave Fauth and Stephen Moretti for their suggestions.
>
> I don't think I articulated the problem properly so I'll try
> again.
No, actually, you articulated the problem well enough. Steven Moretti gave
you the answer, though. I'll give it again, in slightly longer form.
When you use Verity against a database - and it doesn't matter whether it's
Oracle or another database - you use it differently than you would to index
files. You write an SQL query which will return the primary keys and fields
that you want to search for all rows in the table or join. You execute that
query within a CFQUERY. Then, you use CFINDEX with the TYPE attribute set to
CUSTOM. This will instruct Verity to build a searchable index of the records
in the table.
Then, when you search across that index with CFSEARCH, Verity will return
the primary keys for the matching records. You then take those keys and use
them to query the database directly. This will generally be much faster than
the SQL required to search the database directly.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~~~~~~~~~~~~ Paid Sponsorship ~~~~~~~~~~~~~
Get Your Own Dedicated Win2K Server! Instant Activation for $99/month w/Free
Setup from SoloServer PIII600 / 128 MB RAM / 20 GB HD / 24/7/365 Tech Support
Visit SoloServer, https://secure.irides.com/clientsetup.cfm.
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
