From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: minor cleanup in plpgsql.sgml |
Date: | 2003-11-30 05:36:39 |
Message-ID: | 200311300536.hAU5adk11454@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Tom Lane wrote:
> Robert Treat <xzilla(at)users(dot)sourceforge(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-11-30 06:10:03 | Re: PG_VERSION in pg_config.h.win32 |
Previous Message | Joe Conway | 2003-11-30 05:08:53 | export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question) |