pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Ansley <Michael.Ansley@intec-telecom-systems.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: plpgsql grief
Date: Mon, 12 Feb 2001 12:40:25 -0500
Message-ID: <19051.981999625@sss.pgh.pa.us> (raw)
In-Reply-To: <7F124BC48D56D411812500D0B747251480F3FE@FILESERVER002>
References: <7F124BC48D56D411812500D0B747251480F3FE@FILESERVER002>

Michael Ansley <Michael.Ansley@intec-telecom-systems.com> 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



view thread (14+ messages)

Message-ID: <19051.981999625@sss.pgh.pa.us>
Permalink:  ../19051.981999625@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/19051.981999625@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, Michael.Ansley@intec-telecom-systems.com
  Subject: Re: plpgsql grief
  In-Reply-To: <19051.981999625@sss.pgh.pa.us>
  References: <7F124BC48D56D411812500D0B747251480F3FE@FILESERVER002> <19051.981999625@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox