HP3000-L Archives

October 1999, Week 4

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:
Mike Hornsby <[log in to unmask]>
Reply To:
Mike Hornsby <[log in to unmask]>
Date:
Mon, 25 Oct 1999 08:53:14 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
Friedrich wrote,

>How can I make sure, that the sequence of records stored in a TI detail
dataset, corresponds to the >time, when they are entered?
>
> I do not want TI to reuse the space of a deleted record, but to add the
new entry at the end of the set.
It depends on the definition of the word 'sure' and what you intent is.

If the intent is for performance reasons you do not want the disk IO
associated with reusing a deleted record then simply enable the HWMPUT
feature in DBUTIL, or better yet programmatically by:

* THIS TURNS ON HWMPUT DYNAMICALLY!
CALL "DBCONTROL" USING DBNAME, DBDUMMY, MODE9, DBSTATUS.

If the intent is to be 100% 'sure' that DBGET returns the records in the
exact sequence that they were originally added then you have to add a time
date stamp or a sequence counter. I prefer to read and sort on this field
over specifying it as a sort item on a path. But this choice is highly
application dependent.

Even if entries are originally added at the High water mark it is very risky
to rely on this sequence for mode 2 DBGET for future sequential retrieval.
Other applications may be added later that are intended to 'fix up' fields
that DBDELETE & DBPUT entries.

Mike Hornsby
Beechglen Development Inc.
Enterprise Solutions & Support
www.beechglen.com
513-922-0509

ATOM RSS1 RSS2