RE: Suggestion with SQL query -- JAVA400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: Suggestion with SQL query
From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
Date: Mon, 5 Nov 2007 10:37:07 -0600
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the iSeries / AS400 <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

From: Joe Pluta

SELECT t1.id, t1.type, COALESCE(t2.value, t1.value)
FROM t1 LEFT OUTER JOIN t2 ON t1.id = t2.id and t1.type = t2.type

That ought to do the trick. Basically, if there is a row in T2, t2.value
will be used. Otherwise, t2.value will be NULL and t1.value will be used.

Nothing against Michael's UNION technique, either, this technique just seems
a little more straightforward to me. But that's the thing about SQL; there
are often several ways to do the same thing, and the performance of each
technique may be influenced by the data in the files.

Joe

Follow-Ups:

RE: Suggestion with SQL query , Michael_Schutte

This mailing list archive is Copyright 1997-2026 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.