Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f77IU5611337 for ; Tue, 7 Aug 2001 14:30:05 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f77ITuY08889; Tue, 7 Aug 2001 14:29:56 -0400 (EDT) To: "Josh Berkus" cc: mbenzid@yahoo.de (Mounir Benzid), pgsql-sql@postgresql.org Subject: Re: Why can't I ......... In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Tue, 07 Aug 2001 09:34:10 -0700" Date: Tue, 07 Aug 2001 14:29:56 -0400 Message-ID: <8886.997208996@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200108/109 X-Sequence-Number: 4330 "Josh Berkus" writes: >> -- use labels to name columns in this way >> >> ... select col1 userid, col2 name from ... (instead of using AS) > Because AS is the ANSI SQL 92 standard. And we like standards. Actually, SQL92 says that AS is optional. However, Postgres contains a lot of extensions to SQL92, and some of them produce parse ambiguities if AS is optional. So we require it. This isn't going to change, as it would require ripping out a lot of useful stuff. regards, tom lane