From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Yves Dorfsman <yves(at)zioup(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: SELECT INTO and ON COMMIT |
Date: | 2015-05-14 01:04:03 |
Message-ID: | CANu8FiyFxVxBnPdeHK=3kU+HxRkfy09oh11yggvSBzVOO7J+6A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
So perhaps replace the SQL SELECT INTO with SQL ADD INTO ?
On Wed, May 13, 2015 at 8:54 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > On Wed, May 13, 2015 at 06:05:43PM -0600, Yves Dorfsman wrote:
> >> Will `SELECT INTO` be deprecated? It is very convenient when writing
> pgplsql
> >> functions, to select into a record.
>
> > The pl/psql `SELECT INTO` is not related to the SQL SELECT INTO command
> > --- yeah, confusing, so no, the pl/psql ability is not deprecated.
>
> Part of the argument for deprecating the SQL-level SELECT INTO is
> exactly that it's confusingly spelled the same as plpgsql's SELECT INTO,
> but it means something totally different.
>
> regards, tom lane
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-05-14 02:19:19 | Re: SELECT INTO and ON COMMIT |
Previous Message | Tom Lane | 2015-05-14 00:54:07 | Re: SELECT INTO and ON COMMIT |