Dear Tom and Neil,
Thanks very much for your help, and your explanations. This makes a lot
of sense, and I agree - this bug is definitely invalid.
Tom Lane wrote:
> "Richard Neill" <postgresql(at)richardneill(dot)org> writes:
>>SELECT instrument,priceband,pounds FROM tbl_instruments,tbl_prices WHERE
>>ERROR: column reference "priceband" is ambiguous
>>I think that the first query ought to succeed, since although priceband is
>>ambiguous (it could mean either tbl_prices.priceband or
>>tbl_instruments.priceband), the information in the WHERE clause means that
>>they are explicitly equal, and so it doesn't matter which one we use.
> Doing that would be contrary to the SQL specification, AFAICS.
> However, you can get the effect you want by writing the query like
> SELECT instrument,priceband,pounds FROM
> tbl_instruments JOIN tbl_prices USING (priceband);
> which both provides the join condition and logically merges the two
> input columns into just one output column.
> regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Jason Erickson||Date: 2005-03-15 05:53:12|
|Subject: BUG #1545: LIBPQ Windows Version not calling WSACleanup for every WSAStartup|
|Previous:||From: Tom Lane||Date: 2005-03-14 18:39:59|
|Subject: Re: BUG #1542: pg_dump seg fault |