Re: SQL vs native access (was: Record name the same as the filename)

[rob@xxxxxxxxx]

While you may think it is silly there are business cases for this.  In our 
case we have a common routines library - ROUTINES.  We also will be 
supporting several divisions that use this library.  Some of these 
divisions will be using BPCS 405CD, some BPCS 8.  In BPCS 8 they changed 
numerous file structures, including KEY sizes!  With an SQL based solution 
the same program can support both.  With a native rpg access - you cannot.

Another business case.  A die hard native person did some time trials and 
was stunned to find the sql faster.  However he decided to stick with 
native anyway.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





"Joep  Beckeringh" <joep.beckeringh@xxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
08/20/2003 05:01 PM
Please respond to RPG programming on the AS400 / iSeries
 
        To:     "RPG programming on the AS400 / iSeries" 
<rpg400-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        SQL vs native access (was: Record name the same as 
the file name)


SQL was never designed for random access; it was designed for working with
sets. That is why I think it is silly to use SQL for things like file
maintenance ('give me the set of all the customers whose customer number 
is
12345').

Joep Beckeringh

----- Original Message -----
From: "DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>
To: "'RPG programming on the AS400 / iSeries'" <rpg400-l@xxxxxxxxxxxx>
Sent: Wednesday, August 20, 2003 9:15 PM
Subject: RE: Record name the same as the file name


> I hear what you are saying, Bob, but I think you missed my point.  There
is
> no new feature to be had here.  We can already use a SQL table in RPG by
> renaming the format to be unique.
>
> Even if the compiler team developed this, it still doesn't address the
> biggest problem with using SQL tables as native access files in RPG, and
> that is the lack of an integrated index in the table object.  Because 
SQL
> seperates the access path from the view, there's no way access keys,
making
> random access impossible.
>
> Eric DeLong
> Sally Beauty Company
> MIS-Project Manager (BSG)
> 940-898-7863 or ext. 1863

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.