> I have an interesting Verity problem that I am hoping someone can help me
> with - despite scouring the net and trawling through my CFTALK archives I am
> dumbfounded by this problem.
>
> I have set up Verity to index the contents of a database - sounds simple
> enough - I do the query to extract the records and then CFINDEX populates
> the Verity collection from that query.
>
> The problem is that some records are not appearing in searches.
>
> An analysis of the problem reveals these symptoms. The body of the record
> that constitutes the body in CFINDEX is defined in SQL Server as a 'text'
> field. When I open the database in Enterprise Manager I can see the actual
> contents of some of these field for some rows. Some show the content but
> some show <Long Text> - it is the rows that are showing <Long Text> that are
> not getting indexed. All rows appear in the application when called quite Ok
> despite this.

Are you sure this is a Verity problem? Do the full values for those
records show up if you use CFQUERY to fetch them and CFDUMP to display
them?

Have you configured the datasource to allow long text to be retrieved?
By default, there's a fairly short cutoff value for long text. You can
change that in your datasource's advanced settings.

Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/

Fig Leaf Software provides the highest caliber vendor-authorized
instruction at our training centers in Washington DC, Atlanta,
Chicago, Baltimore, Northern Virginia, or on-site at your location.
Visit http://training.figleaf.com/ for more information!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to 
date
Get the Free Trial
http://ad.doubleclick.net/clk;207172674;29440083;f

Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:321987
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to