Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f08NsnB47952 for ; Mon, 8 Jan 2001 18:54:49 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f08NsVJ20181; Mon, 8 Jan 2001 18:54:31 -0500 (EST) To: "Robert B. Easter" cc: Jens Hartwig , Tod McQuillin , Nikolaj Lundsgaard , pgsql-sql@postgresql.org Subject: Re: Sv: how to build this query ??? Please help !!! In-reply-to: <0101081836221J.09559@comptechnews> References: <3A545AF2.1C827233@debis.com> <0101081724411I.09559@comptechnews> <0101081836221J.09559@comptechnews> Comments: In-reply-to "Robert B. Easter" message dated "Mon, 08 Jan 2001 18:36:22 -0500" Date: Mon, 08 Jan 2001 18:54:31 -0500 Message-ID: <20178.978998071@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200101/80 X-Sequence-Number: 741 "Robert B. Easter" writes: > The query I did was bad syntax I guess. No, it's just a bug. PG accepts GROUP BY items that are references to output columns, cf. http://www.postgresql.org/devel-corner/docs/postgres/sql-select.htm Looks like it gets confused when the grouped-by item contains a subselect, however. regards, tom lane