×
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.
I think, with indexes as you have described, that the join approach would be most efficient. Have you tried both approaches to determine their relative performance? Visual explain could be helpful in this respect...
-Eric DeLong
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Luis Rodriguez
Sent: Thursday, May 14, 2009 11:09 AM
To: Midrange-L
Subject: SQL View - Embedded Select vs Join
I've been asked to write a view that shows the name or description for each one of the FileA codes.
As I see it, I can write the view as sequence of join files:
-----------------
SELECT A.*, B.State_Name as State_Name1, C.State_Name as State_Name2,
D.Cust_Description as Cust1, E.Cust_Description as Cust2
FROM FileA as A
LEFT OUTER JOIN File1, File2 B on A.State_Code1 = B.State_Code
LEFT OUTER JOIN File1, File2 C on A.State_Code1 = C.State_Code
LEFT OUTER JOIN File1, File3 D on A. Cust_Code1= C. Cust _Code
LEFT OUTER JOIN File1, File3 E on A. Cust_Code1= E. Cust _Code
-----------------
OR, I can write it using a Select for each ânameâ field:
-----------------
Select A.*,
(Select State_Name from File2 b where A.State_Code1 = B.State_Code) As State_Name1,
(Select State_Name from File2 c where A.State_Code2 = C.State_Code) As State_Name2,
â
etc., etc,
FROM File1 as A
-----------------------
Which option would you think is more efficient? Interestingly enough, a small test I did with only one field yielded exactly the same results on Visual Explain.
Thanks in advance,
Luis Rodriguez
IBM Certified Systems Expert
eServer i5 iSeries Technical Solutions
As an Amazon Associate we earn from qualifying purchases.
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.