X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 07AB2474E5C for ; Tue, 25 Feb 2003 14:16:21 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 65568-03 for ; Tue, 25 Feb 2003 14:16:10 -0500 (EST) Received: from news.hub.org (news.hub.org [64.49.215.80]) by postgresql.org (Postfix) with ESMTP id AAA1E475458 for ; Tue, 25 Feb 2003 14:15:05 -0500 (EST) Received: by news.hub.org (Postfix, from userid 8) id 7F84643A666; Tue, 25 Feb 2003 14:15:05 -0500 (EST) From: Edmund Lian X-Newsgroups: comp.databases.postgresql.sql Subject: Re: Denormalizing during select Message-ID: References: <200302241433.49502.josh@agliodbs.com> X-Newsreader: Forte Agent 1.91/32.564 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 11 Date: Tue, 25 Feb 2003 18:48:19 GMT X-Complaints-To: abuse@cox.net Organization: Cox Communications To: pgsql-sql@postgresql.org X-Virus-Scanned: by amavisd-new X-Archive-Number: 200303/8 X-Sequence-Number: 12048 On Tue, 25 Feb 2003 03:44:02 GMT, Edmund Lian wrote: >I found this example in "Practical PostgreSQL"... will it do the job? Answering my own question: kind of. The problem with custom aggregates is that they need to be used with a "group by" clause, and this means that the select cannot return columns that are not aggregates of some kind. What I'm trying to return are rows that are a combination of columns and aggregates. ...Edmund.