Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id AAA18775; Tue, 29 Feb 2000 00:59:38 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id AAA10605; Tue, 29 Feb 2000 00:59:12 -0500 (EST) From: Bruce Momjian Message-Id: <200002290559.AAA10605@candle.pha.pa.us> Subject: Re: [HACKERS] Re: [SQL] prob with aggregate and group by - returns multiplesh In-Reply-To: <27957.951803062@sss.pgh.pa.us> from Tom Lane at "Feb 29, 2000 00:44:22 am" To: Tom Lane Date: Tue, 29 Feb 2000 00:59:12 -0500 (EST) CC: Thomas Lockhart , "'pgsql-sql@postgresql.org'" , PostgreSQL Development X-Mailer: ELM [version 2.4ME+ PL72 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > 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? It was me. Informix uses it. > > 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. -- Bruce Momjian | http://www.op.net/~candle pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026