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 13728.1112714541@sss.pgh.pa.us
Whole thread Raw
In response to Re: Should we still require RETURN in plpgsql?  (Robert Treat)
Responses Re: Should we still require RETURN in plpgsql?  (Oleg Bartunov)
List pgsql-hackers
Robert Treat <> writes:
> While it is useless in this example, istm it only makes things more
> confusing to require return in some cases but not in others.  Is there
> some technical advantage to dropping it?

It's about the same either way as far as the code is concerned.  But
I've only written a dozen or so plpgsql functions using OUT parameters,
and I've already found having to write a useless RETURN to be tedious
(not to mention that I forgot it a couple times).  I don't think I'll be
the last one complaining if we leave in the requirement.

Basically the requirement exists to make sure you don't forget to define
the return value.  But when you're using OUT parameters, the existence
of a RETURN statement has nothing to do with defining the return value.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [GENERAL] plPHP in core?
Next
From: "Marc G. Fournier"
Date:
Subject: Re: [GENERAL] plPHP in core?