Mark M wrote:
If I'm updating/refreshing a Verity index, and someone goes to search
the collection while it is doing that, will Verity hold off from
giving a result until that is done, or will it pass back an error?

i.e. Do I need to lock the two events (index, and search) with a
named lock? to ensure on will wait for the other, and they won't
collide?

Although this was true of older versions of Verity (c.CF4.5) it is not true of the current Verity SDK. No locking is required.

With regard to what result you will get -- basically the update is performed on the older version of the INDEX. If you choose to update by using REFRESH you may get unexpected results as REFRESH effectively purges the entire collection first.

-- geoff
http://www.daemon.com.au/


--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to