Re: minor cleanup in plpgsql.sgml - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: minor cleanup in plpgsql.sgml
Date
Msg-id 200311300536.hAU5adk11454@candle.pha.pa.us
Whole thread Raw
In response to Re: minor cleanup in plpgsql.sgml  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Tom Lane wrote:
> Robert Treat <xzilla@users.sourceforge.net> writes:
> > Funny. That's a good argument for doing it that way, but almost the same
> > argument I make for putting the INTO at the end: so as to not confuse
> > people with the "SELECT a,b,c INTO newtable FROM oldtable" sql syntax.
> > In either case ISTM the existing recommendation is flawed.
>
> Come to think of it, I think that the motivation for the existing
> recommendation was precisely to have a syntax that is visibly different
> from the SQL-level SELECT INTO, with an eye to eventually allowing the
> SQL construct to work too.  This may not be very important though,
> considering that SELECT INTO is deprecated in favor of CREATE TABLE AS.

I have removed the recommentation:

    <para>
     The <literal>INTO</> clause can appear almost anywhere in the <command>SELECT</command>
     statement.
    </para>


--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: Joe Conway
Date:
Subject: export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question)
Next
From: Bruce Momjian
Date:
Subject: Re: PG_VERSION in pg_config.h.win32