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

From Robert Treat
Subject Re: minor cleanup in plpgsql.sgml
Date
Msg-id 1069779243.22025.240.camel@camel
Whole thread Raw
In response to Re: minor cleanup in plpgsql.sgml  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
On Tue, 2003-11-25 at 11:24, Tom Lane wrote:
> Robert Treat <xzilla@users.sourceforge.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.
>
>             regards, tom lane

guess that was an unconscious change made on my part. I tend to use that
format for writing functions since I feel it is more clear to read.

Actually if I had my druthers I'd probably remove that "advice"
entirely, but either way that change can be disregarded, but removal of
the "full_name varchar" line should still be done.

Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL


pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: minor cleanup in plpgsql.sgml
Next
From: Neil Conway
Date:
Subject: Re: minor cleanup in plpgsql.sgml