Hi Z. Yes, indeed it does take some doing, but it can be done...and I am doing it. When I am indexing my large queries ( I have one with 40,000 records) I break the query down into pieces using a method that could definitely use some improvement. First, I get a recordcount. Than I divide the number of records by four and then I do four seperate queries using BETWEEN statements for the record ID. This way, I wind up getting approximately equal groups of 4 queries that I then index to seperate verity collections. (Actually, because of the time it takes to index so many records, I had to set it up so that only one section would occur at at a time.) There is probably a better way to do this, but this is how I do it and it does work. You may want to take this back to the list and see if anyone else comes up with any other ideas. I don't know of any other search engines you can integrate with Cold Fusion, so unless you have knowledge that some other language will work better, verity is the way to go. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, May 18, 2000 9:20 PM Subject: Verity > Thanks for all your info on the benefits and what to look out for when > using verity. The one question I'm left with is after you pointed me to > the allaire kb article I read it and saw that the verity bundled with cf > can't handle collections (the actual files not the index) over 100 MB. > Now if I was only dealing with documents that would be no problem > because I could break it up into many collections all lesss than 100 MB > and feed them all into a verity search, but when creating a verity > collection on a database table I don't see how that could be done and a > database table (from a multi-join) for a large sight could easily be > over 100 MB. > --Z > > ------------------------------------------------------------------------------ Archives: http://www.eGroups.com/list/cf-talk 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.
