× 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.


  1.  Home
  2. MIDRANGE-L
  3. March 2005

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.