HP3000-L Archives

June 2003, Week 3

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:
From:
fred White <[log in to unmask]>
Reply To:
fred White <[log in to unmask]>
Date:
Mon, 16 Jun 2003 19:05:39 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (43 lines)
On Monday, June 16, 2003, at 03:02 PM, [log in to unmask] wrote:

> Dear Fred:
>
> I seem to remember that this movement of data only occurs in a MASTER
> set (manual or automatic), not a detail.

Your memory is good. Detail entries are never moved except by utilities.

Master entries may be moved but only if they are Secondaries (of a
Synonym chain) and only under one of the following two circumstances:

1. A DBDELETE of a Primary entry which has one or more Synonyms. In
this case, the first Synonym is MOVED to the Primary address to become
the new Primary of that Synonym chain.

2. A DBPUT which discovers that the correct Primary address for this
new entry is occupied by a Secondary of some other Synonym chain. In
this case, DBPUT finds an empty location and MOVES that Secondary to
this new location and changes the pointers of the predecessor and
successor (if any) of that MOVED Secondary. Finally, DBPUT stores the
new Primary in the location formerly occupied by the MOVED Secondary.

>
> Delete a chain of detail entries on causes the backward/forward
> pointers to be longer pointing to the deleted record. The deleted
> detail entry becomes part of the delete chain for that detail set?

YES.

>
> Am I completely deluded?

No. Except for a couple of typos in that last paragraph.

FW

P.S. I've sent this to the list in case others want to know this
information.

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

ATOM RSS1 RSS2