I found the bug with this -- it's in cfa_propertyindexkeyupdate.cfm.
Line 57:
<cfindex action="refresh"
collection="#attributes.property#"
key="ObjectID"
type="CUSTOM"
title="ObjectName"
query="attributes.qPropertyData"
body="PropertyValue"
custom1="TypeID"
custom2="Property"
>
The action for the cfindex should actually be UPDATE. Otherwise it purges
everything from the collection first.
That's no good if:
1) You're using a property for multiple types
2) You're using the webtop type indexing which indexes types in multiple
steps -- each step would wipe out the collection, resulting in only those
objects indexed by the last step being saved.
In addition, Line 54 has a CFLOCK, but the docs for CFINDEX say not to use
CFLOCK when using the UPDATE action. I don't know if the CFLOCK should come
out or not. Comments?
Is this the right place to report bugs, or do I have to do it through
spectrasource.macromedia.com?
Derk
-----Original Message-----
From: Derek Westfall [mailto:[EMAIL PROTECTED]
Sent: Friday, April 04, 2003 6:17 AM
To: Spectra-Talk
Subject: RE: Verity indexing problem
The other weird thing is that if I index object type X and those objects
start showing up in searches, then subsequently index object type Y, the
objects from type Y may start showing up but the ones from X no longer do.
Then I index Type X and type Y doesn't show up.
Many of my types share the same property definition (like Title, Body). Is
that wrong?
Derek
______________________________________________________________________
Get the mailserver that powers this list at http://www.coolfusion.com
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
