Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id CEE88476F60 for ; Fri, 15 Nov 2002 11:11:43 -0500 (EST) Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (Postfix) with ESMTP id 1E819476E8F for ; Fri, 15 Nov 2002 10:42:30 -0500 (EST) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 61F95D68D; Fri, 15 Nov 2002 07:42:24 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 539375C0B; Fri, 15 Nov 2002 07:42:24 -0800 (PST) Date: Fri, 15 Nov 2002 07:42:24 -0800 (PST) From: Stephan Szabo To: Huub Cc: Subject: Re: Error message: standard SQL or PostgreQSL? In-Reply-To: Message-ID: <20021115073908.R9290-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200211/229 X-Sequence-Number: 10371 On Fri, 15 Nov 2002, Huub wrote: > Hi, > > When I copied a function call into an SQL-statement and executed it, I > got the message 'Aggregate function calls may not be nested'. Does that > mean this is the case in standard SQL or is this specifically PostgreSQL? Umm, both sort of. It's an entry level SQL92 restriction IIRC, so both allowing it and not allowing it are standard SQL to some degree.