From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SQL procedures |
Date: | 2017-11-08 14:31:57 |
Message-ID: | CAFj8pRAnWbUcp3sPvrLSq7xrsnao5SGOW9ma=zyNq6_xpUHRtw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2017-11-08 15:23 GMT+01:00 Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com>:
> On 10/31/17 16:50, Pavel Stehule wrote:
> > Not sure if disabling RETURN is good idea. I can imagine so optional
> > returning something like int status can be good idea. Cheaper than
> > raising a exception.
>
> We could allow a RETURN without argument in PL/pgSQL, if you just want
> to exit early. That syntax is currently not available, but it should
> not be hard to add.
>
> I don't understand the point about wanting to return an int. How would
> you pass that around, since there is no declared return type?
>
We can create auto session variable STATUS. This variable can be 0 if
procedure was returned without explicit RETURN value. Or it can hold
different value specified by RETURN expr.
This value can be read by GET DIAGNOSTICS xxx = STATUS
or some similar.
> --
> Peter Eisentraut http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2017-11-08 14:33:51 | Re: SQL procedures |
Previous Message | Merlin Moncure | 2017-11-08 14:23:51 | Re: SQL procedures |