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

Up. Anybody will answer on this bug report?

2009/1/21 Oleg Serov <serovov(at)gmail(dot)com>

> Sorry, but is not important, i forgot to remove original table name
> "chunk_ad", but is not affected to the bug..
>
> 2009/1/21 Oleg Serov <serovov(at)gmail(dot)com>:
> > Here is an example:
> >
> > CREATE TABLE test2 (
> > id BIGINT,
> > chunk_id BIGINT
> > );
> > CREATE TABLE test1 (
> > id BIGINT
> > );
> >
> > CREATE OR REPLACE FUNCTION "bug" () RETURNS pg_catalog.void AS
> > $body$
> > DECLARE
> > row_test1 test1%rowtype;
> > row_test2 test2%rowtype;
> > BEGIN
> > SELECT test1, chunk_ad
> > FROM test1 JOIN test2 ON(chunk.id = test2.chunk_id)
> > LIMIT 1
> > INTO row_test1, row_test2;
> >
> > END;
> > $body$
> > LANGUAGE 'plpgsql' VOLATILE CALLED ON NULL INPUT SECURITY DEFINER;
> >
> > Will throw error:
> > ERROR: LIMIT #,# syntax is not supported
> > HINT: Use separate LIMIT and OFFSET clauses.
> > QUERY: SELECT test1, chunk_ad FROM test1 JOIN test2 ON(chunk.id =
> > test2.chunk_id) LIMIT 1, 0, $1
> > CONTEXT: SQL statement in PL/PgSQL function "bug" near line 8
> >
> > ********** Ошибка **********
> >
> > ERROR: LIMIT #,# syntax is not supported
> > SQL state: 42601
> > Подсказка:Use separate LIMIT and OFFSET clauses.
> > Контекст:SQL statement in PL/PgSQL function "bug" near line 8
> >
>

--
С уважением

Олег Серов