From: wieck@debis.com
To: marten@feki.toppoint.de
Cc: tgl@sss.pgh.pa.us
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] HAVING in EXISTS-clause ...
Date: Sat, 13 Nov 1999 04:17:30 +0100 (MET)
Message-ID: <m11mTgw-0003l1C@orion.SAPserv.Hamburg.dsh.de> (raw)
In-Reply-To: <199911120755.IAA05120@feki.phoenix-edv.netzservice.de>
>
> 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).
Nervous or not, Tom is right!
Some people seem to forget that Postgres initially was a
PostQUEL database. After the original Berkeley project
terminated, it became a SQL database and (sometimes) later
called PostgreSQL.
The PostQUEL query language was way simpler than SQL. All the
internal structures of Postgres where optimized to match this
language.
We need to change a detail in the parser/rewriter now, to
meet the needs of our new language. This requires changes not
only in the parser and rewirter, the planner/optimizer and
maybe the executor need changes too. Usually, this kind of
vertical change takes some time in open source projects.
But it doesn't help to continue doing cosmetic changes on the
symptoms. Sometimes you have to attack the initial problems,
and this time is now.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck@debis.com (Jan Wieck) #
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: wieck@debis.com, marten@feki.toppoint.de, tgl@sss.pgh.pa.us
Subject: Re: [SQL] HAVING in EXISTS-clause ...
In-Reply-To: <m11mTgw-0003l1C@orion.SAPserv.Hamburg.dsh.de>
References: <199911120755.IAA05120@feki.phoenix-edv.netzservice.de> <m11mTgw-0003l1C@orion.SAPserv.Hamburg.dsh.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox