Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f1CHeRx35362 for ; Mon, 12 Feb 2001 12:40:27 -0500 (EST) (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.1/8.11.1) with ESMTP id f1CHeP919054; Mon, 12 Feb 2001 12:40:25 -0500 (EST) To: Michael Ansley cc: pgsql-sql@postgresql.org Subject: Re: plpgsql grief In-reply-to: <7F124BC48D56D411812500D0B747251480F3FE@FILESERVER002> References: <7F124BC48D56D411812500D0B747251480F3FE@FILESERVER002> Comments: In-reply-to Michael Ansley message dated "Mon, 12 Feb 2001 17:19:46 +0000" Date: Mon, 12 Feb 2001 12:40:25 -0500 Message-ID: <19051.981999625@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/223 X-Sequence-Number: 1414 Michael Ansley writes: > I thought that the discussion on this topic resolved that the AS syntax > would work as I described, and the INTO syntax would be removed because of > ambiguity, to be redeveloped at a later date? INTO has indeed been removed. However, AS does not do what you seem to think it does; in fact, it is entirely a noise clause in this context. regards, tom lane