Received: from localhost (IDENT:root@hectic-2.jpl.nasa.gov [128.149.68.204]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA79391; Wed, 1 Mar 2000 01:04:17 -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 GAA13247; Wed, 1 Mar 2000 06:14:51 GMT Sender: lockhart@hub.org Message-ID: <38BCB55B.AC175BB9@alumni.caltech.edu> Date: Wed, 01 Mar 2000 06:14:51 +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: <200002291719.MAA26261@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > So are we willing to field questions from people trying to use TEMP > tables and trying TEMP and not TEMPORARY. I realize the restriction on > a field called TEMP, but we don't get those very often. How many people > are going to guess TEMP and not TEMPORARY? Well, that's one reason to stick to a published standard. No guessing required since one could look it up ;) - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California