> Well, I know you like the SQL Server text indexing quite a bit, but in
more than just having thai btw.
> fairness, these aren't serious issues in most of the search functionality
> I've seen. You're free to cache what you like, after it comes back from
*after* on the cf box.
> to that of SQL Server. As for joining back to the indexed table, you're
> right, although in most cases I'm not sure I'd want to join back to that
> table - I just want to show the results in a drill-down interface, and let
since i *can* do these things, i tend to *do* these things.
> more information right away, it's pretty trivial to simply query the
> database using the Verity keys. The same goes for combining it with other
2 queries vs 1. i win.
> I admit that, given a choice, I might go with SQL Server's indexing, but I
> don't know whether I'd justify purchasing SQL Server for a project for
that
no its not but my backends are almost always sql server.
> whether you can do in SQL Server's text indexing, like spidering sites and
> indexing filesystem contents (although I suspect that if one knew enough
um i win again (just call me cash money ;-)
SELECT Q.DocTitle, DATEPART(YEAR, Q.Create)
FROM OPENQUERY(FileSystem,
'SELECT DocTitle, Create
FROM SCOPE('' "/pubs" '')
WHERE BookCost <= 20.00
AND CONTAINS( Characterization, '' "ice hockey" '' )
') AS Q
______________________________________________________________________
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
