Two questions. Can you replicate this more than once?
Are you using CFMX7? If so, can you add a status="foo" variable to you index and dump the results? For those who don't know, you can now get status info after you perform an index operation. This is a helpful way to detect a problem with indexing. -Raymond Camden, ray.camdenfamily.com On 8/16/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Well, I determined that in my case below, I had 48 records that were > duplicate keys. By making all my keys unique, I ended up with the desired > result. > > My concern, and wondering about whether there is a potential bug in CFINDEX > or not, is why did CF drop the last 48 records of the original query instead > of dropping the 48 duplicate keys? The 48 duplicates were included in my > CFSEARCH results, so they were added to the index. > > I found another instance of this happening to another developer as well. > > Has anyone else experienced these results, and anyone know why in the world > CFINDEX would act this way and is it intentional and, if so, why? > > Thanks, > > Dave > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:215241 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
