On Wed, Jan 21, 2009 at 01:37:39PM +0100, Emil Obermayr wrote:
> I am not sure what the standard says, but I am used to single columns
> after a natural join. So if table a and b are joined through column c
> the following statement is valid:
>
> select c from a natural join b;
bad example, becau
On Wed, Jan 21, 2009 at 07:40:53AM -0500, Igor Tandetnik wrote:
>
> Can you just write "select a.c from a natural join b;" ?
Of course, but the DB-application is already written and is used by
other DBs also. The application design currently needs the column to be
unique without the need to speci
"Emil Obermayr" wrote in
message news:20090121123739.gc15...@nobswolf.info
> I am not sure what the standard says, but I am used to single columns
> after a natural join. So if table a and b are joined through column c
> the following statement is valid:
>
> select c from a natural join b;
>
> But
I am not sure what the standard says, but I am used to single columns
after a natural join. So if table a and b are joined through column c
the following statement is valid:
select c from a natural join b;
But I get "SQL error: ambiguous column name: c"
Can this behaviour be changed? Will it be
4 matches
Mail list logo
