Re: SQL vs. traditional I/O?

[michaelr_41@xxxxxxxxxxxxxx]

It depends on the type of processing. Most business systems are
transactional and access a record (row) at a time. There's no advantage
to creating an SQL cursor to access one record - traditional file I/O is
better. Processing a set of data is much better done using SQL than
traditional I/O.

On Thu, 22 Jul 2004 13:16:38 -0500, "Bob Cagle" <bcagle@xxxxxxxxxxx>
said:
> 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
> 
> 
> 
> --
> 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.
> 
-- 
  
  michaelr_41@xxxxxxxxxxxxxx