|
Now, why in the world would you even consider doing that? The SQL implementation in RPG is "clunky" at best - that's already been agreed upon. Why make the program harder to read/maintain when you would get the same performance? -----Original Message----- From: Mark S. Waterbury [mailto:mark.s.waterbury@xxxxxxx] Sent: Thursday, July 22, 2004 10:51 PM To: Midrange Systems Technical Discussion Subject: Re: SQL vs. traditional I/O? Hi, all: Here's a "radical" idea -- would it not be "cool" if IBM could make the embedded SQL pre-processor "smart enough" to recognize when you are doing "single row at a time" types of things, and under the covers, actually generate "native" I/O? ;-) Mark S. Waterbury -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.