Re: Yet another SQL newbie question -- MIDRANGE-L

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

Subject: Re: Yet another SQL newbie question
From: "James H H Lampert" <jamesl@xxxxxxxxxxx>
Date: Thu, 24 Nov 2005 15:24:45 -0800
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

rob@xxxxxxxxx wrote:

A join is not the same as a union.

to which I replied:

True, but based on Richard Casey's suggestion, it looksvery much like a join could be an adequate (if INSANELYverbose) stand-in for an INTERSECT:

. . . which is indeed the case. I've now got the UNION andINTERSECT cases working rather well, and will most likelyget the EXCEPT case working Friday.

Thanks, Rob, Richard, et al., for all your help with thisproject. Although I'm sure it ain't over yet.


--
JHHL

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.