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



Problem solved...programmer error. Sigh...

Anyway, an inner join is the default anyway, right?

On Mon, Nov 23, 2009 at 11:21 AM, Michael Ryan <michaelrtr@xxxxxxxxx> wrote:

Hmmm...when I copy the statement (filling in the variables with values)
from my RPG program to interactive SQL, it works in interactive SQL. I *do*
have multiple records in FILEA with the same key value, and only one record
with that key value in FILEB.


On Mon, Nov 23, 2009 at 11:04 AM, Terrence Enger <tenger@xxxxxxxxxxxxxxxx>wrote:

On Mon, 2009-11-23 at 10:34 -0500, Michael Ryan wrote:
If I have FILEA and FILEB with a matching key of FILEA.KEY and
FILEB.KEY,
wouldn't this:

Select * from FILEA Inner Join FILEB on FILEA.KEY = FILEB.KEY

Give me all the records where there is a match in FILEA and FILEB, and
no
other records?

That sounds right. If you are seeing more records than you were
expecting, it may be the result of a repeated value in the KEYs.
Remember that join means (some subset of) the cross product of the
tables.

Cheers,
Terry.


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




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.