| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: RETURNS TABLE returns NULL set when called by another RETURNS TABLE |
| Date: | 2010-02-24 07:06:39 |
| Message-ID: | 162867791002232306h29bb12ccx1d69b0e7e6423bab@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
2010/2/24 Josh Berkus <josh(at)agliodbs(dot)com>:
>
>> val1 is just as ambiguous. I think you got bit by the name collision;
>> the output parameters would start out NULLs and thus lead to the
>> described behavior, in versions before 9.0.
>
> Aha, yeah, that's probably it. Take this example as the reason we had
> to change the behavior ...
yes - I am very happy with this change. It is the biggest change in
plpgsql over 10 years.
Pavel
>
> --Josh Berkus
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zoltan Kovacs | 2010-02-24 10:30:22 | BUG #5345: non-administrator users cannot create databases with special encoding |
| Previous Message | Pavel Stehule | 2010-02-24 07:03:02 | Re: RETURNS TABLE returns NULL set when called by another RETURNS TABLE |