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 BAA26182; Tue, 29 Feb 2000 01:40:29 -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 GAA11084; Tue, 29 Feb 2000 06:48:06 GMT Sender: lockhart@hub.org Message-ID: <38BB6BA6.B5FACCAD@alumni.caltech.edu> Date: Tue, 29 Feb 2000 06:48:06 +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: Bruce Momjian CC: Tom Lane , "'pgsql-sql@postgresql.org'" , PostgreSQL Development Subject: Re: [HACKERS] Re: [SQL] prob with aggregate and group by - returns multiplesh References: <200002290559.AAA10605@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > If not, I'd vote for pulling it out. That's a heck of a poor word to > > reserve. > I am afraid of lots of user complaints, even if we had not already used > TEMP. OK, but we've already got "user complaints" about TEMP being a reserved word, so that part seems to balance out. There is apparently no basis in published standards for TEMP being a reserved word. And btw it is not currently documented as a reserved word in syntax.sgml... - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California