RE: SQL explained

Simple,

It's best practice now-a-days....for any DB, including DB2 on the iSeries.

Before you are correct, RPG had a problem with it.  But now you can use the 
PREFIX keyword to handle RPG's limitation.

HTH,

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Steve Landess
> Sent: Wednesday, March 30, 2005 11:29 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: SQL explained
> 
> 
> > Rob wrote:
> >  For example some of the code presented is V5R3.  Prior to V5R3
> >  LEFT OUTER JOIN CUSTMAST USING (SLSPSN))
> > Would have had to be written as
> >  LEFT OUTER JOIN CUSTMAST ON SLSPSNF.SLSPSN = CUSTMAST.SLSPSN)
> > Now, many people might still have to use this method 
> because (IMNSHO) of a
> > poor design standard of naming the fields differently.  Example
> >  LEFT OUTER JOIN CUSTMAST ON SLSPSNF.SLSLSP = CUSTMAST.CSSLSP)
> 
> Rob - since when did it become a "best practice" to use the 
> same field name 
> multiple files?
> 
> I have alway been taught that it is NOT a best practice, 
> particularly since 
> in RPG if the field names are the same, the buffer storage 
> occupied by the 
> field is global, and by READing or CHAINing you could 
> accidently overlay the 
> value of a field in one file with the value of the same field 
> in another 
> file, causing unpredictable results.
> 
> Care to explain your reasoning?
> 
> Regards,
> Steve
> 
> -- 
> 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.
> 
>