From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: minor cleanup in plpgsql.sgml |
Date: | 2003-11-25 19:24:20 |
Message-ID: | Pine.LNX.4.44.0311252022350.11097-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Tom Lane writes:
> Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> > ! SELECT INTO users_rec * FROM users WHERE user_id=3;
> > --- 986,993 ----
> > ! SELECT * FROM users WHERE user_id=3 INTO users_rec;
>
> Why do you want to change the example to disagree with the advice given
> just above?
>
> : At present, the INTO clause can appear almost anywhere in the SELECT
> : statement, but it is recommended to place it immediately after the
> : SELECT key word as depicted above. Future versions of PL/pgSQL may be
> : less forgiving about placement of the INTO clause.
Well, that position is a strange choice. The standard syntax of SELECT
INTO in embedded SQL is
SELECT a, b, c INTO :x, :y, :z FROM ...
This should probably be consistent.
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2003-11-25 20:33:51 | Re: preliminary: logical column order |
Previous Message | Peter Eisentraut | 2003-11-25 19:12:10 | Re: Install pg_config_manual.h |