Re: Verity creating duplicate records - Please help

[Judith Taylor]

Casye,

I think part of the problem here is that you're expecting Verity to behave 
dynamically. It doesn't.

  When you create a Verity collection, Verity creates a set of flat files 
in which to store the collection data. It does not go in and update your 
collection automagically, you have to do it yourself. Verity is not a 
database like SQL or Access. It doesn't matter if you go into your database 
and delete an individual record, or update it.

Unless you purge your Verity collection and then update it, Verity will not 
know that a change has been made.
If you make a single change to a record, you have to purge the entire 
record and then update it. If you simply update it, Verity will treat the 
changed record as simply another record and add it to the existing collection.

If you have Ben Forta's book, Chapter 29 has a section on maintaining your 
Verity collections.

Also, regarding the custom fields, you can't put in more than one field. It 
simply doesn't work.

Casey Giles put into words:
Hi Judith and All,

 From what I got out of the docs with CFINDEX the 'Purge' action should
delete ALL the records in the collection, 'update' should update any
records you pass in, and if it cant find a record for a particular key
you send; it will create a new record.

The problem is that it's not finding the record that already exists and
is creating duplicates...But only in this one collection, surely the
fact that it IS updating all the other 4 collections I have is proof
that it should work this way all the time.

I tried deleting an existing individual record before updating it, but
verity couldnt find the key to delete it. But yet it finds all the keys
when searching on them! I guess the collection is in some way corrupt to
behave this way, but I cant pin point why; when it seems to be fully
populated and searching fine (until I want to update or delete a key).

Does anyone else have any suggestions, Im really need to figure this one
out. A scheduled task fixes this daily but it really isnt nice for
people to see two results for the same article.

Is there any way a verity collection could get corrupted by what data
you feed into it? Are there limits to how long a field can be ?(Im
filling the 2 custom fields with long comma delimited lists)

Any help at all would be greatly appreciated...

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/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Re: Verity creating duplicate records - Please help

[Casey Giles]

Hi Judith and All,

From what I got out of the docs with CFINDEX the 'Purge' action should
delete ALL the records in the collection, 'update' should update any
records you pass in, and if it cant find a record for a particular key
you send; it will create a new record.

The problem is that it's not finding the record that already exists and
is creating duplicates...But only in this one collection, surely the
fact that it IS updating all the other 4 collections I have is proof
that it should work this way all the time.

I tried deleting an existing individual record before updating it, but
verity couldnt find the key to delete it. But yet it finds all the keys
when searching on them! I guess the collection is in some way corrupt to
behave this way, but I cant pin point why; when it seems to be fully
populated and searching fine (until I want to update or delete a key).

Does anyone else have any suggestions, Im really need to figure this one
out. A scheduled task fixes this daily but it really isnt nice for
people to see two results for the same article.

Is there any way a verity collection could get corrupted by what data
you feed into it? Are there limits to how long a field can be ?(Im
filling the 2 custom fields with long comma delimited lists) 

Any help at all would be greatly appreciated...

Thanks
Casey Giles

Web Developer
B4Bsport.com


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.


Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists