Received: from localhost (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.9.3/8.9.3) with ESMTP id AAA13063; Tue, 29 Feb 2000 00:38:10 -0500 (EST) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id FAA10658; Tue, 29 Feb 2000 05:48:12 GMT Sender: lockhart@hub.org Message-ID: <38BB5D9C.ED50B126@alumni.caltech.edu> Date: Tue, 29 Feb 2000 05:48:12 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: Peter Eisentraut CC: Tom Lane , George Dau , "'pgsql-sql@postgresql.org'" , PostgreSQL Development Subject: Re: [HACKERS] Re: [SQL] prob with aggregate and group by - returns multiples References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > 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... - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California