On Sat, 7 May 2005, Jochem van Dieten wrote:
On 5/7/05, Dan Bolser wrote:
On Sat, 7 May 2005, Jochem van Dieten wrote:
On 5/7/05, Dan Bolser wrote:
select pk from a inner join b using (pk);
ERROR 1052 (23000): Column 'pk' in field list is ambiguous!!!
Is this a bug, or is it like this
Hi!
Dan Bolser wrote:
[[...]]
I would have said...
select pk from a inner join b on a.pk = b.pk;
(probably pk was a bad choice for an example column name).
Using the ON syntax instead of the USING syntax makes my problem look even
more silly than it already is, i.e. just say
select a.pk from a
On 5/7/05, Dan Bolser wrote:
Why are columns included in the join between two tables ambigious?
Because MySQL does not follow the SQL standard (ISO/IEC 9075-2:2003).
select pk from a inner join b using (pk);
ERROR 1052 (23000): Column 'pk' in field list is ambiguous!!!
Is this a bug,
On 5/7/05, Chris wrote:
Somethign else to think about as well, look at this slight modification:
select pk from a left join b using (pk);
Now, it's not likely this is a valid query for your table structure
It is very likely it is. It is even an example in the MySQL manual.
but, in
On Sat, 7 May 2005, Jochem van Dieten wrote:
On 5/7/05, Dan Bolser wrote:
Why are columns included in the join between two tables ambigious?
Because MySQL does not follow the SQL standard (ISO/IEC 9075-2:2003).
select pk from a inner join b using (pk);
ERROR 1052 (23000): Column 'pk' in
On 5/7/05, Dan Bolser wrote:
On Sat, 7 May 2005, Jochem van Dieten wrote:
On 5/7/05, Dan Bolser wrote:
select pk from a inner join b using (pk);
ERROR 1052 (23000): Column 'pk' in field list is ambiguous!!!
Is this a bug, or is it like this for a reason? It drives me nuts, because
it is
Why are columns included in the join between two tables ambigious?
It seems that they should *not* be ambigious!
Like this
select pk from a inner join b using (pk);
ERROR 1052 (23000): Column 'pk' in field list is ambiguous!!!
Is this a bug, or is it like this for a reason? It drives me
a and b respectively.
Rhino
- Original Message -
From: Dan Bolser [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Friday, May 06, 2005 6:50 PM
Subject: amPiguous!
Why are columns included in the join between two tables ambigious?
It seems that they should *not* be ambigious
06, 2005 6:50 PM
Subject: amPiguous!
Why are columns included in the join between two tables ambigious?
It seems that they should *not* be ambigious!
Like this
select pk from a inner join b using (pk);
ERROR 1052 (23000): Column 'pk' in field list is ambiguous!!!
Is this a bug, or is it like
tables a and b respectively.
Rhino
- Original Message -
From: Dan Bolser [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Friday, May 06, 2005 6:50 PM
Subject: amPiguous!
Why are columns included in the join between two tables ambigious?
It seems that they should
in the
select statement?
Rhino
- Original Message -
From: Dan Bolser [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Friday, May 06, 2005 6:50 PM
Subject: amPiguous!
Why are columns included in the join between two tables ambigious?
It seems that they should *not* be ambigious!
Like
this could
become somewhat tricky with the ON syntax.
-Simon
- Original Message -
From: Dan Bolser [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Friday, May 06, 2005 6:50 PM
Subject: amPiguous!
Why are columns included in the join between two tables ambigious?
It seems
Bolser [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Friday, May 06, 2005 6:50 PM
Subject: amPiguous!
Why are columns included in the join between two tables ambigious?
It seems that they should *not* be ambigious!
Like this
select pk from a inner join b using (pk);
ERROR 1052 (23000
= b.col2
Of course, you need to replace 'a.col1' and 'b.col2' with real column names
from tables a and b respectively.
Rhino
- Original Message -
From: Dan Bolser [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Friday, May 06, 2005 6:50 PM
Subject: amPiguous!
Why
:14 PM
Subject: Re: amPiguous!
On 7/05/2005 11:00 a.m., Rhino wrote:
Actually, the error message is misleading. There is nothing that I would
call ambiguous in your query: you have a syntax error. The join should
be
written:
select pk from a inner join b on a.col1 = b.col2
Somethign else to think about as well, look at this slight modification:
select pk from a left join b using (pk);
Now, it's not likely this is a valid query for your table structure,
but, in this instance, a.pk and b.pk are not necessarily the same. b.pk
could potentially be NULL while a.pk was
16 matches
Mail list logo
