HP3000-L Archives

January 2003, Week 5

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: SIGIMAGE Update: HP R&D Lab still open
From:
Roy Brown <[log in to unmask]>
Reply To:
Roy Brown <[log in to unmask]>
Date:
Tue, 28 Jan 2003 11:45:09 -0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines) 
Wirt Atmar wrote:

> Nor is there any reason to have any sort of flag with CIUPDATE turned
> permanently on (or at least on by default). Unless the user is somehow
> philosophically depending on the current CIUPDATE or DBUPDATE
> procedures to intentionally screw up his extended sorts, installing
> newly corrected procedures that honor those extended sorts cannot
> possibly do him any harm.

Not true. A user who has, but doesn't care about, extended sorts, can rely on
his records not moving in a DBUPDATE when the extended sort fields are all
that he changes.

With extended sorts honoured, the records may relocate in the chain, causing
them to be processed twice by chain handling logic which may not be expecting
a recurrence of the record.

e.g. a chain of nine records has a field in the extended sort area with
1,2,3,,,, 9 in its entries. Process 'add 10 to each entry in this field' and
DBUPDATE down the chain. Currently, it will wind up with 11....19 in there.

Honouring extended sort fields without warning, it will only terminate when
the field overflows.

--
Roy Brown
Posting with the OEnemy, tamed by OE-QuoteFix 1.18.3
http://jump.to/oe-quotefix

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2