HP3000-L Archives

August 1995, 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:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Thu, 24 Aug 1995 17:30:53 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
Jeff writes:
 
> We discussed this many months ago, and many felt (and I still do) that the
> old dbinfo() capacity should return the max capacity for DDX-enabled sets,
> not the currently-allocated capacity.  In the current implementation, the
 
What if DDX expansion was triggered when the #available entries in the
dataset drops to, say, 1 (or 10 or 20?), instead of when it drops
to 0?
 
Thus, if an application says:
 
   if #entries_in_set < current_capacity then
      do real work
   else
      complain
 
that application will be work correctly with DDX.
 
The only "too-smart" application that wouldn't work is one that says:
 
   if #entries_in_set + #I_intend_to_add <= current_capacity then
      do real work
   else
      complain
 
Because, if #I_intend_to_add > 1 (or 10 or 20), the "early expansion trigger"
above wouldn't be quite enough.
 
 
--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html

ATOM RSS1 RSS2