RE: SQL within application programs

Of course, if the only thing you need is to get one record using one
index, CHAIN will be faster, but if selection criteria for this single
record are more complicated, SQL will have essetially the same
performance and it is much easier to program.

On the other side, if you have a kind of real-time program and you are
desperate to shave off a millisecond or two, then probably SQL is not an
option - but how many applications of this type do you know ?

    Best regards,

          Alexei Pytel



> -----Original Message-----
> From: Mary Koetting [SMTP:Mary_Koetting@mail.mchcp.org]
> Sent: Tuesday, December 15, 1998 11:09 PM
> To:   'midrange'
> Subject:      SQL within application programs
> 
> When is it efficient  to use SQL within application programs? 
> 
> It has been my thinking that if a subset of records can be selected at
> one
> time, it would be time effective use of SQL but if one and only one
> record
> is being sought, dynamic access would be faster. 
> 
> Any thoughts/opinions on the matter.  Any and all greatly appreciated.
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---