Ben Cornwell

Most people working with postgres have probably encountered something like this before:

SELECT
instrument,
priceband,
pounds
FROM   tbl_instruments,
tbl_prices
WHERE   tbl_instruments.priceband=tbl_prices.priceband;
ERROR:  column reference "priceband" is ambiguous

Although that’s normal behavior according to the SQL standard, and very easy to fix using ‘tbl_instruments.priceband’ in the SELECT, it kind-of doesn’t make sense given that WHERE clause: both tbl_instruments.priceband and tbl_prices.priceband will yeild the same value. I found the following in the Postgres mailing archives (imo, a much neater solution than qualifying the column names):

SELECT
instrument,
priceband,
pounds
FROM
tbl_instruments
JOIN
tbl_prices USING (priceband);

 
 

Recently

	
Cleaning Up After CruiseControl
	
CITCON
	
Fail
	
PHPUnderControl (Install cont.)
	
PistaDex
	
PHPUnderControl Install Guide
	
Bianchi Pista
	
Eastlink (plus to & from)
	
Velo-Rage
	
On Cycling
	

 



You can follow any responses to this entry through the RSS 2.0 feed.



You can leave a response, or trackback from your own site.