Subject: | |
From: | |
Reply To: | |
Date: | Fri, 25 Aug 1995 12:49:27 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Bruce writes:
...
> if a DDX-aware application calls
> DBINFO mode 205, discovers that there really ought to be room, and starts
> its updates, it's no less susceptable to the out-of-disc-space failure than
> the DDX-ignorant application that gets the right answer from the
> hypothetical changed DBINFO mode 202.
Ah, but the application programmer *knows* that an out-of-disc-space during
expansion is possible ... and the application's design should take that
into account.
If the application positively, absolutely wants to enter "all or none",
it can do today:
DBXBEGIN
DBLOCK
DBINFO 202.
If enough, put them all
If not enough, DBINFO 205
If enough:
put dummy entries;
if success, delete them and put real entries
else complain and backout.
DBXEND
NOTE: I've not written an application that does the above, but at least
it is possible!
--
Stan Sieler [log in to unmask]
http://www.allegro.com/sieler.html
|
|
|