From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michal Szymanski <dyrex(at)poczta(dot)onet(dot)pl>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to use RETURN TABLE in Postgres 8.4 |
Date: | 2009-07-03 15:49:42 |
Message-ID: | 162867790907030849q6272901eufba275b2223856b2@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2009/7/3 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Michal Szymanski <dyrex(at)poczta(dot)onet(dot)pl> writes:
>> CREATE OR REPLACE FUNCTION buggy_procedure() RETURNS TABLE (id INT8,
>> test VARCHAR)
>> AS $$
>> BEGIN
>> -- @todo hide password
>> RETURN QUERY
>> SELECT id ,test
>> FROM bug_table
>> ;
>> END;
>> $$
>> LANGUAGE plpgsql STRICT SECURITY DEFINER;
>
> Don't use column names in your functions that are the same as variable
> or parameter names of the function. This is working basically as if
> you'd written "SELECT null,null", because the output parameters are
> still null when the RETURN QUERY is executed.
>
use qualified names instead
RETURN QUERY
SELECT b.id, b.test
FROM bug_table b;
regards
Pavel Stehule
> regards, tom lane
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | nha | 2009-07-03 16:37:40 | Re: Group by on %like% |
Previous Message | Tom Lane | 2009-07-03 15:46:38 | Re: How to use RETURN TABLE in Postgres 8.4 |