Re: BUG #6031: Bug with plpgsql function and RETURNS TABLE - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #6031: Bug with plpgsql function and RETURNS TABLE
Date
Msg-id 1305922486-sup-532@alvh.no-ip.org
Whole thread Raw
In response to BUG #6031: Bug with plpgsql function and RETURNS TABLE  ("Preston M. Price" <preston@clearwateranalytics.com>)
List pgsql-bugs
Excerpts from Preston M. Price's message of vie may 20 12:12:09 -0400 2011:

> If I create a plpgsql function and use RETURNS TABLE
> the returned result set is filled with null values rather than the values
> from the table.

> select * from TEST_FUNC();
>
> This query yields 5 rows of null rather than the values from the test table.

Yeah, known problem.  Don't use the column name as variable name; or you
can qualify the column name in the query, like this:

alvherre=# CREATE or replace FUNCTION TEST_FUNC() RETURNS TABLE(val int) AS $$
BEGIN
    RETURN QUERY SELECT test.val FROM test;
END;
$$ LANGUAGE plpgsql;
CREATE FUNCTION

alvherre=# select * from TEST_FUNC();
 val
-----
   1
   2
   3
   4
   5
(5 filas)


--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-bugs by date:

Previous
From: "Preston M. Price"
Date:
Subject: BUG #6031: Bug with plpgsql function and RETURNS TABLE
Next
From: "Emmanuel"
Date:
Subject: BUG #6032: server fail to connect