Re: BUG #5352: Bug in PL/PgSQL "SELECT .. INTO" statement parser

From: Alex Hunsaker <badalex(at)gmail(dot)com>
To: Oleg <serovov(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5352: Bug in PL/PgSQL "SELECT .. INTO" statement parser
Date: 2010-03-01 15:24:28
Message-ID: 34d269d41003010724s7f51e4d2uebb2f9143617f890@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Mar 1, 2010 at 02:22, Oleg <serovov(at)gmail(dot)com> wrote:
> CREATE OR REPLACE FUNCTION "bug" () RETURNS pg_catalog.void AS
> $body$
> DECLARE
>   row_test1 test1%rowtype;
>   row_test2 test2%rowtype;
> BEGIN
>   SELECT test1, chunk_id
>       FROM test1 JOIN test2 ON(chunk.id = test2.chunk_id)
>       LIMIT 1
>       INTO row_test1, row_test2;

*shrug* it works if you put the INTO after SELECT. From the manual:

http://www.postgresql.org/docs/current/static/plpgsql-statements.html#PLPGSQL-SELECT-INTO

: The INTO clause can appear almost anywhere in the SQL command.
Customarily it is written either just before or just
: after the list of select_expressions in a SELECT command, or at the
end of the command for other command types.
: It is recommended that you follow this convention in case the
PL/pgSQL parser becomes stricter in future versions.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2010-03-01 15:49:07 Re: BUG #5352: Bug in PL/PgSQL "SELECT .. INTO" statement parser
Previous Message Robert Haas 2010-03-01 14:50:59 Re: BUG #5338: PG_DUMP fails due to invalid adnum value