RE: SQL vs. traditional I/O?

Bob,

Of course, this is just my opinion, but, I wouldn't say that there's a need
to move to 100% SQL. The "simple chain to a logical file" works fine in most
situations (I would like to be able to use that simple chain in some other
programming platforms). However, what about those situations that you don't
have a logical in that order? When you need to process a subsetted group of
records? In the past, that would be OPNQRYF. Well, now it can be done with
SQL as well. I don't really like Query/400. Not that it's a bad package. I
just prefer SQL over it. Maybe I am biased...well, I am. But, maybe I have
no real reason to be :). We've done many things with embedded SQL that has
made my job so much easier. I would have a heck of a time taking that tool
out of my toolbox. But, I have no reason to drop the traditional I/O either.

It may be that others want to move to 100% SQL so they can point their
package at another database. I've no need to do that at the present time.
Nor, do I really relish the idea of doing that in the future.

-Kevin

-----Original Message-----
From: Bob Cagle [mailto:bcagle@xxxxxxxxxxx]
Sent: Thursday, July 22, 2004 11:17 AM
To: Midrange Systems Technical Discussion
Subject: SQL vs. traditional I/O?


Maybe I'm opening a bucket of worms here, but for straight RPG
programming on an AS400/iSeries/i5 machine, why should we use SQL
instead of traditional RPG I/O (read, chain, etc.)?  I have seen
multiple postings on these lists and several articles all saying we need
to switch to SQL now!  But, traditional I/O works great on the platform
it was intended for - the SQL implementations I have seen are 'clunky'
at best.

Note: I understand SQL has its place; web programming, etc.  I just
don't see the need to switch over 100% to SQL.  What am I missing?  Why
should I use an SQL select statement versus a simple chain to a logical
file?

Bob Cagle

#####################################################################################
Attention:
The information contained in this message and or attachments is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material.  Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient
is prohibited. If you received this in error, please contact the sender and
delete the material from any system and destroy any copies.

Thank You.
#####################################################################################