Received: from meryl.it.uu.se (root@meryl.it.uu.se [130.238.12.42]) by hub.org (8.9.3/8.9.3) with ESMTP id FAA92438; Tue, 29 Feb 2000 05:54:17 -0500 (EST) (envelope-from e99re41@DoCS.UU.SE) Received: from Svan.DoCS.UU.SE (e99re41@Svan.DoCS.UU.SE [130.238.9.160]) by meryl.it.uu.se (8.8.5/8.8.5) with ESMTP id LAA14683; Tue, 29 Feb 2000 11:54:07 +0100 (MET) Received: from localhost (e99re41@localhost) by Svan.DoCS.UU.SE (8.6.12/8.6.12) with SMTP id LAA14557; Tue, 29 Feb 2000 11:54:06 +0100 X-Authentication-Warning: Svan.DoCS.UU.SE: e99re41 owned process doing -bs Date: Tue, 29 Feb 2000 11:54:06 +0100 (MET) From: Peter Eisentraut Reply-To: Peter Eisentraut To: Thomas Lockhart cc: Tom Lane , George Dau , "'pgsql-sql@postgresql.org'" , PostgreSQL Development Subject: Re: [HACKERS] Re: [SQL] prob with aggregate and group by - returns multiples In-Reply-To: <38BB5D9C.ED50B126@alumni.caltech.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 29 Feb 2000, Thomas Lockhart wrote: > > > Postgres thinks that TEMP is a keyword, so it won't take it as a table > > > name unless you put quotes around it. > > This is really an unfortunate case where someone should have read the SQL > > standard before putting in a feature. The SQL keyword is TEMPORARY, and > > TEMP is really a popular name for a dummy table. > > So why not yank TEMP and require TEMPORARY? Saving an extra 5 > characters of typing is not a good enough reason to keep it imho, and > if the SQL92 standard requires a particular form why bother extending > it? > > A major release is a good time to adjust syntax to promote > compliance... I've been (lightly) bashed in the past for proposing such things (see END/ABORT) but I'm with you. I think that TEMP may be far too wide-spread by now, though. -- Peter Eisentraut Sernanders vaeg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden