Subject: | |
From: | |
Reply To: | |
Date: | Fri, 5 Sep 1997 11:43:37 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Rick Brooks writes:
>>> Rick Brooks <[log in to unmask]> 09/05/97 10:26am >>>
I'd like to ask a follow-up to Gary's question...
Are there any situations, especially when dealing with datasets with a
large number of puts, deletes, (and the occasional Detpack), that the
'LIFO' order of a detail chain cannot be relied upon? I have always
thought of this as a general rule, but I haven't had the 'faith' to
rely on it and code based on that logic. Is my lack of faith prudent
or sinful?
-----------------------------------------------------------------------------------
Absolutely there are occasions when 'LIFO' cannot be relied on. Unless
you use a sort item of a transaction count, date or other means to
identify the order that items were added for each chain that you expect
'LIFO' to apply, you chain order will be hosed by changing of the search
item of the key you need 'LIFO' on. This can be by DBDELETE/DBPUT, or
by DBUPDATE with CIU on.
When using sort items, don't forget about extended sort items that may
also change the order on the chain. Extended sort items do not reorder
the chain if they are changed on DBUPDATE without also changing the
sort field. In this instance you must use DBDELETE/DBPUT to make
extended sort items work.
Mike Berkowitz
Guess? Inc.
|
|
|