Ok, this way works and the proposed way isn't necessary.
On 5/24/06, Tom Lane <[EMAIL PROTECTED]> wrote:
"John Jawed" <[EMAIL PROTECTED]> writes:
> I guess I don't understand what one has to do with the other (SRF's
> returning records and OUT parameters). I always thought they were exclusive,
>
Tom,
> If you write something like
>
> create function foo (in p1 int, out r1 int, out r2 text)
> returns setof record
D'oh! I feel like a dork now. I forgot we had this.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast)--
"John Jawed" <[EMAIL PROTECTED]> writes:
> I guess I don't understand what one has to do with the other (SRF's
> returning records and OUT parameters). I always thought they were exclusive,
> could you elaborate?
(BTW, please don't post uselessly HTML-ified mail.)
If you write something like
I guess I don't understand what one has to do with the other (SRF's returning records and OUT parameters). I always thought they were exclusive, could you elaborate?On 5/24/06,
Tom Lane <[EMAIL PROTECTED]> wrote:
Josh Berkus writes:>> I've been working on a function which retu
Josh Berkus writes:
>> I've been working on a function which returns a setof a composite type.
>> Everytime I've changed the structure of the returning setof, I've had to
>> change the type accordingly, which current means doing a drop type ...
>> cascade down to the function. We should allow one
Makes more sense to do that, and I think it'll be cleaner to implement as well.On 5/23/06, Josh Berkus wrote:John,> I've been working on a function which returns a setof a composite type.
> Everytime I've changed the structure of the returning setof, I've had to> change the typ
John,
> I've been working on a function which returns a setof a composite type.
> Everytime I've changed the structure of the returning setof, I've had to
> change the type accordingly, which current means doing a drop type ...
> cascade down to the function. We should allow one of the following: