Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id AAA14386; Tue, 29 Feb 2000 00:44:32 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id AAA27960; Tue, 29 Feb 2000 00:44:22 -0500 (EST) To: Thomas Lockhart cc: "'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> References: <38BB5D9C.ED50B126@alumni.caltech.edu> Comments: In-reply-to Thomas Lockhart message dated "Tue, 29 Feb 2000 05:48:12 +0000" Date: Tue, 29 Feb 2000 00:44:22 -0500 Message-ID: <27957.951803062@sss.pgh.pa.us> From: Tom Lane Thomas Lockhart writes: >> 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? Probably we ought to stop to ask why TEMP is in there to begin with; perhaps for compatibility with some other RDBMS? If not, I'd vote for pulling it out. That's a heck of a poor word to reserve. regards, tom lane