X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
	by postgresql.org (Postfix) with ESMTP id E676611F6004
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Fri, 28 Apr 2006 12:59:52 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
	with ESMTP id 37633-09
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Fri, 28 Apr 2006 12:59:29 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from mail.logix-tt.com (unknown [212.211.145.186])
	by postgresql.org (Postfix) with ESMTP id 264DD11F600C
	for <pgsql-sql@postgresql.org>; Fri, 28 Apr 2006 12:59:29 -0300 (ADT)
Received: from kingfisher.intern.logix-tt.com (T9c46.t.pppool.de
	[89.55.156.70])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.logix-tt.com (Postfix) with ESMTP id A9D0E656C8
	for <pgsql-sql@postgresql.org>; Fri, 28 Apr 2006 18:00:33 +0200 (CEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by kingfisher.intern.logix-tt.com (Postfix) with ESMTP id 79919184C9BC0
	for <pgsql-sql@postgresql.org>; Fri, 28 Apr 2006 17:59:45 +0200 (CEST)
Message-ID: <44523BF1.1080307@logix-tt.com>
Date: Fri, 28 Apr 2006 17:59:45 +0200
From: Markus Schaber <schabi@logix-tt.com>
Organization: Logical Tracking and Tracing International AG, Switzerland
User-Agent: Debian Thunderbird 1.0.7 (X11/20051017)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: PostgreSQL SQL List <pgsql-sql@postgresql.org>
Subject: Slightly confused error message
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200604/206
X-Sequence-Number: 25015

Hi,

I just stumbled over a slightly confused error message:

mydb=# select count(*),coverage_area from myschema.streets except select
cd as coverage_area from countryref.disks group by streets.coverage_area;
ERROR:  column "streets.coverage_area" must appear in the GROUP BY
clause or be used in an aggregate function

As the query looks, streets.coverage_area is actually used in the GROUP BY.

I know how to fix the query, but I wonder whether it is worth the effort
to try improving the error message.

Thanks,
Markus
-- 
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org