Re: Results and questions, Re: Something lighter than a databasefile . . .

you could do a setll on the file and check for %error.
 

----- Original Message ----- 
From: James H H  <mailto:jamesl@xxxxxxxxxxx> Lampert 
To: Midrange Systems Technical  <mailto:midrange-l@xxxxxxxxxxxx> Discussion 
Sent: Thursday, March 09, 2006 8:37 PM
Subject: Results and questions, Re: Something lighter than a databasefile .
. .


Well, our experiment with replacing the temporary file 
with a combination of a *USRIDX and a *DTAQ didn't pan 
out. In a real-world test, it was either not much better, 
or even slightly worse. 

One thing, though (and this is starting to look like time 
to transfer the thread to the RPG list): 

We did determine that writing a duplicate key to a file 
(and allowing it to fail) was a real killer on speed. Is 
there a "cheap" way to check for a duplicate key without 
writing, and that works when you're trying to read the 
file sequentially even as you're adding to it? 

I vaguely remember something about the relative costs of 
different record-level/native database operations. I don't 
remember whether it was on this list, or the RPG list, or 
in a magazine, or a Redbook, or elsewhere, but I do 
remember something about examples that did exactly the 
same thing in different ways, and ran at dramatically 
different speeds.