Re: RETURNS TABLE returns NULL set when called by another RETURNS TABLE

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: RETURNS TABLE returns NULL set when called by another RETURNS TABLE
Date: 2010-02-24 03:37:00
Message-ID: 4B849EDC.2040101@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


> 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 ...

--Josh Berkus

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2010-02-24 03:55:47 Re: BUG #5344: pg_restore some foreign keys missing
Previous Message Tom Lane 2010-02-24 03:34:38 Re: RETURNS TABLE returns NULL set when called by another RETURNS TABLE