Skip site navigation (1) Skip section navigation (2)

Should we still require RETURN in plpgsql?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Should we still require RETURN in plpgsql?
Date: 2005-04-05 06:28:23
Message-ID: 10266.1112682503@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
As of CVS tip, plpgsql handles output parameters, in the style

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 RETURN statement is kinda useless in this example, but it is still
required, because we don't allow control to fall off the end of a
plpgsql function without causing an error.

I am thinking we should allow exit by falling off the end of the
function when (a) it has output parameter(s), or (b) it is declared
"RETURNS void".  Comments?

How does Oracle's PL/SQL handle this?

			regards, tom lane

Responses

pgsql-hackers by date

Next:From: Christopher Kings-LynneDate: 2005-04-05 06:40:22
Subject: Re: Should we still require RETURN in plpgsql?
Previous:From: Tom LaneDate: 2005-04-05 05:02:32
Subject: Re: DELETE ... USING

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group