RE: Something lighter than a database file . . .

 Files in QTEMP reside in memory. There is something in the code/applciation 
design that is "bottlenecking" the process. Joe--- On Mon 03/06, James H H 
Lampert < jamesl@xxxxxxxxxxx > wrote:From: James H H Lampert [mailto: 
jamesl@xxxxxxxxxxx]To: midrange-l@xxxxxxxxxxxxxxxx: Mon, 06 Mar 2006 17:23:20 
-0800Subject: Something lighter than a database file . . .Would anybody have 
any suggestions for something that would:1. Be lighter than a temporary 
database file, preferably living in memory, instead of on disk, and having less 
overhead than a file,2. Yet still be capable of expanding to contain whatever 
data records are put into it,3. While rejecting duplicate records?We've got a 
server job that turns a single client request for a sort of "mass dump" (cf. a 
SysEx dump in MIDI) into a bunch of, shall I say, "simulated client requests," 
storing them in a database file in QTEMP. The simulated requests then run as a 
batch, with the results sent back to the client as a single 
response. It's an improvement over having the client generate the whole list of 
requests as if they were being sent interactively, but we have reason to 
believe the database file is bottlenecking the process.--JHHL-- This is the 
Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo post a 
message email: MIDRANGE-L@xxxxxxxxxxxxxx subscribe, unsubscribe, or change list 
options,visit: http://lists.midrange.com/mailman/listinfo/midrange-lor email: 
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx posting, please take a moment to review 
the archivesat http://archive.midrange.com/midrange-l.

_______________________________________________
No banners. No pop-ups. No kidding.
Make My Way  your home on the Web - http://www.myway.com