You need to purge your collection before you update it. In the docs, it
states that Verity will do just what you are describing.
I have a little demo that I did for our local CFUG (MidOhioValley) where I
have this little tidbit:
<CFINDEX ACTION="PURGE">
This action basically deletes all the data in the collection/index, but
leaves all the necessary infrastructure in place ready to be re-populated
with new data. It is important to perform this action after updating a
database to ensure that you don't end up with duplicate, and possibly
erroneous, data.
Mind you, I did this for database indexing, not file indexing.
Oh, the URL is http://lacer.cf-developer.net/VerityDemo/index.cfm
HTH,
Judith
>Gday
>
>For some reason when I try to update one of my collections with changes
>to a single record, verity is creating a new record with the SAME key (a
>spectra objectid) rather than updating the collection for that record.
>So Im getting multiple results referring to the same object in my search
>results. The call to cfindex is exactly the same, whether initially
>populating the index with all the records or updating this single
>record... the only difference is there is only 1 record in the query
>when updating a single record.
>
>The data in each record is going in fine, and this is working with my
>other collections.
Judith Taylor
ICQ: 67460562
Freelance ColdFusion Developer - Athens, OH
Friends don't let friends code before coffee.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
