Re: Should we still require RETURN in plpgsql? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Should we still require RETURN in plpgsql?
Date
Msg-id 10862.1112687019@sss.pgh.pa.us
Whole thread Raw
In response to Re: Should we still require RETURN in plpgsql?  (Dennis Bjorklund <db@zigo.dhs.org>)
Responses Re: Should we still require RETURN in plpgsql?  (Robert Treat <xzilla@users.sourceforge.net>)
List pgsql-hackers
Dennis Bjorklund <db@zigo.dhs.org> writes:
> On Tue, 5 Apr 2005, Tom Lane wrote:
>> CREATE FUNCTION sum_n_product(x int, y int, OUT sum int, OUT prod int) AS $$
>> BEGIN
>> sum := x + y;
>> prod := x * y;
>> RETURN;
>> END;
>> $$ LANGUAGE plpgsql;

> The above code example do not have any RETURNS clause, does that mean that 
> it defaults to RETURNS void?

No, it effectively "RETURNS record", where the particular record type is
implied by the set of output parameters.  See my previous proposal.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Dennis Bjorklund
Date:
Subject: Re: Should we still require RETURN in plpgsql?
Next
From: Russell Smith
Date:
Subject: Re: [GENERAL] plPHP in core?