|
Charles,
I think that what you wrote is valid when there are two tables. If there is
a third table, How can the SQL interpreter know which table are you
referring to?
In the V6R1 there is a reference to using parentheses when doing multiple
joins, in order to avoid ambiguities. Nevertheless, in the examples
provided they utilize the ON clause and qualify their column names...
Regards,
Luis
Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--
On Thu, Oct 16, 2014 at 3:02 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:
There shouldn't be multiple mykey columns...it
Once Tblb is joined to tbla, there's only 1 mykey column, which should be
available for joing to tblc USING mykey again...and the end result should
have only 1 mykey column.
The USING cluase used to be broke and didn't work like this. IBM fixed
at 6.1. I was happy to hear it as it made the syntax I'm trying to usewrote:
work. Today it doesn't.
Charles
On Thu, Oct 16, 2014 at 3:25 PM, Alan Campin <alan0307d@xxxxxxxxx>
coming
You have to give them a reference and say which table the field is
mailingfrom.
select t1.mykey, t1.flda, t2.fldb, t3.fldc
from tbla t1
join tblb t2
on t1.mykey = t2.mykey
join tblc t3
on t1.mykey = t3.mykey
On Thu, Oct 16, 2014 at 1:18 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:
I'm getting SQL0203 - Name MYKEY is ambiguous
with the following:
select mykey, flda, fldb, fldc
from tbla
join tblb using (mykey)
join tblc using (mykey)
^---cursor positioned here...
I've tried adding parens (in various places), but get the same error.
CREATE TABLE QTEMP/TBLA (MYKEY CHAR (10 ) NOT NULL WITH DEFAULT,
FLDA CHAR (10 ) NOT NULL WITH DEFAULT)
CREATE TABLE QTEMP/TBLB (MYKEY CHAR (10 ) NOT NULL WITH DEFAULT,
FLDB CHAR (10 ) NOT NULL WITH DEFAULT)
CREATE TABLE QTEMP/TBLC (MYKEY CHAR (10 ) NOT NULL WITH DEFAULT,
FLDC CHAR (10 ) NOT NULL WITH DEFAULT)
Running 7.1 TR6
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
listlistlist
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.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
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 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.