At 02:29 PM 8/6/99 -0600, John Krussel wrote:
>Not so fast, If any of your programs delete records from the set then new
>entries will be added in the spot where the old records were deleted (Image
>uses the delete chain before the hiwater mark). So in that case they would
>not be in chronological order. Now if you enable HWMPUT in dbutil for that
>base then new records will always be added at the hiwater mark even if there
>is a delete chain so they will be in chronological order.
True, if one were doing a serial read. But the original question involved
doing a DBFIND/DBGET(5) chain read, in which case indeed the entries will
be returned in the order they were added to the path used for the DBFIND
when no sort is defined and no other activity (reorg/unload/reload) is
performed, regardless of the serial order within the physical file.
>
>John Krussel
>Systems Manager
>Nordstrom Direct
>[log in to unmask]
>http://www.nordstrom.com
>
>
>> -----Original Message-----
>> From: Tom Brandt [SMTP:[log in to unmask]]
>> Sent: Friday, August 06, 1999 1:18 PM
>> To: [log in to unmask]
>> Subject: Re: Image Chain Order
>>
>> At 15:59 8/6/99 -0400, Jim Phillops wrote:
>> >Given an Image detail data set in "natural" condition (that is, no
>> >reorg, no DBUNLOAD/DBLOAD, etc. has been performed on the set),
>> >are the records returned in chronological order when DBFINDing by
>> >the primary path and DBGETting them (mode 5)?
>>
>> Assuming also no sort fields, yes, the entries will be returned in
>> chronological order.
>>
>> Tom Brandt Northtech Systems, Inc.
>> +1 734-769-5040 313 N. First Street
>> +1 734-769-5498 (FAX) Ann Arbor, MI 48103
>
X-no-Archive:yes
/jf
_\\///_
(' o-o ')
___________________________ooOo_( )_OOoo____________________________________
Friday, August 6th
Today in 1945 - The 1st atomic bomb was dropped on
Hiroshima, Japan.
___________________________________Oooo_____________________________________
oooO ( )
( ) ) /
\ ( (_/
\_)
|
