×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
--- rpg400-l-request@xxxxxxxxxxxx wrote:
------------------------------
message: 3
date: Thu, 14 Feb 2008 17:42:37 -0600
from: Joe Pluta <j...@xxxxxxxxxxxxxxxxx>
subject: Re: Working with tables, best method
<Big cut here...>
I stand by the fact that single record chains and updates
still
outperform SQL.
<....>
Joe,
(Not trying to begin a long thread here, just being
curious?)
Although, of course, the decision to use either SQL or RPG
(or combination of both) is a business decision, I concur
that Single Record Access (SLA) in RPG is always faster
than SLA in SQL.
My question is, why is this so? If I work with SQLRPGLE,
IBM translates my SQL instructions to an intermediate code,
before compiling my program. Couldn't it be possible to use
a special SQL instruction (e.g. SELECT * FROM TABLE WITH
SLA) and then have the precompiler (either RPG or the DB
interpreter) convert it to a CHAIN (or UPDATE)?. Just
wishful thinking, I know, just wondering?
Regards,
Luis Rodriguez
Luis Rodriguez
IBM Certified Systems Expert
eServer i5 iSeries Technical Solutions
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
midrange.com
