At 01:20 AM 8/9/99 , Steve Dirickson wrote:
>Now for another unclear area: when DBUPDATE with CIUPDATE "ON" is used
>to change the value of the sort item, are the extended sort items also
>examined to properly relocate the record? Or do we need to use
>DBDELETE/DBPUT to change the sort-item value when extended sort items
>are used? I would assume the former, but you know what that does....

Yes... and yes.  :)

DBUPDATE with CIUPDATE enabled essentially just "dbdeletes" and "dbputs"
only on the chain(s) with keys that changed, saving the work of updating
the chains which didn't need changing.  The extended sort items are still
effective.  However, if you change an extended sort item (whether or not
CIUPDATE is enabled) without changing the key which is sorted, the chain is
*not* updated and so the entry doesn't move into the new position based on
the extended sort items.  Another way of saying it is that extended sort
items are used for sorting the chain only when adding an entry to the chain
(either on DBUPDATE with CIUPDATE enabled or on DBPUT) but that otherwise
sorted chains are not guaranteed to be sorted by the extended sort items.
--
Jeff Woods
[log in to unmask]  [PGP key available here via finger]