Postgres Pro
Downloads
Home   >   mailing lists

Re: RETURNS TABLE returns NULL set when called by another RETURNS TABLE - Mailing list pgsql-bugs

From Josh Berkus
Subject Re: RETURNS TABLE returns NULL set when called by another RETURNS TABLE
Date
Msg-id 4B849EDC.2040101@agliodbs.com
Whole thread Raw
In response to Re: RETURNS TABLE returns NULL set when called by another RETURNS TABLE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: RETURNS TABLE returns NULL set when called by another RETURNS TABLE  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-bugs
Tree view 
> 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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: RETURNS TABLE returns NULL set when called by another RETURNS TABLE
Next
From: Robert Haas
Date:
Subject: Re: BUG #5344: pg_restore some foreign keys missing