RE: SQL within application programs

I think of SQL as being good in terms of being able to separate out your
front-end programs from your back-end database.  If all access to the
database was with SQL, you could (in theory) move the database onto another
box (even another platform) and not affect the programs.

Actually (I'm no expert, but), I think of SQL as being rather inefficient
when it comes to complicated queries, etc.

-Branston
EDS - Colorado Springs CO

> -----Original Message-----
> From: Mary Koetting [SMTP:Mary_Koetting@mail.mchcp.org]
> Sent: Tuesday, December 15, 1998 4: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
+---