|
Buck Calabro <mcalabro@commsoft.net> wrote: > Absolutely! Excellent suggestion, although not all 400's have the SQL > development kit. > > Although SQL is itself a welcome abstraction from the physical file layout, > putting the SQL inside an "update" procedure, will allow you to quickly > change from "native" to SQL without impacting the calling code. Using > procedures can let you experiment with the various trade-offs (run time cost A problem with SQL is that one can access the data in whatever sequence one pleases without any reference to database performance. Sure IBM has a SQL optimiser that hunts for indexes that the SQL statement can use, but if the coders are allowed to freely code SQL constructs without regard to the indexes that are needed to support the SQL you can end up with a nightmare. (and them some as I am experiencing ) ____________________________________________________________________ Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com. +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.