|
> From: Buck Calabro > > In order to make SQL perform as nicely as RPG, you need to start at > the beginning, just like we did with RPG. Start with the database > design and proceed from there. I know, I know - who has the time to > do that? Probably none on this list. So what's the point? Not to complain, but you've said things like this several times, Buck. You imply that somehow reorganizing your database will make SQL perform as well as native I/O. I contend, and have been showing, that there are standard operations required for business programming that do not (and probably will never) work as well in SQL as in native I/O. If you disagree, I'd love an example of where a different database design will either: A. Make a single record FETCH as fast as a CHAIN -or- B. Remove the need for single-record access Joe
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.