Received: from mail.toppoint.de (LaForge.toppoint.de [195.244.243.6]) by hub.org (8.9.3/8.9.3) with SMTP id VAA62237 for ; Fri, 12 Nov 1999 21:33:14 -0500 (EST) (envelope-from feki.toppoint.de!marten@toppoint.de) Received: by mail.toppoint.de (Smail3.1.29.1) id ; Sat, 13 Nov 99 03:33 MET Received: (from marten@localhost) by feki.phoenix-edv.netzservice.de (8.9.3/8.9.3) id IAA05120; Fri, 12 Nov 1999 08:55:30 +0100 From: marten@feki.toppoint.de Message-Id: <199911120755.IAA05120@feki.phoenix-edv.netzservice.de> Subject: Re: [SQL] HAVING in EXISTS-clause ... In-Reply-To: <13557.942292816@sss.pgh.pa.us> from Tom Lane at "Nov 10, 1999 11: 0:16 pm" To: tgl@sss.pgh.pa.us (Tom Lane) Date: Fri, 12 Nov 1999 08:55:30 +0100 (CET) Cc: pgsql-sql@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL47 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hello all out there, > involving aggregate functions as sub-selects in FROM. So it's probably > not worth any effort to add more code to a routine that shouldn't exist > in the first place; we've got to work on the fundamental problem What makes me nervous is the fact, that I've seen limitations with the length of the sql statements, some hidden problems here and there and we want to use PostgreSQL in a research projects the next year and we're writing now some oo->rdbms mapper software and therefore we produce some "non-typical" statements and see those limitations (and perhaps even better: some are not documented). Marten