Thank you Pavel, Adrian! That makes a lot of sense. I wasn't aware that in
Oracle you can overload a procedure by its OUT parameters. I had thought in
Postgres procedure overloading would definitely be the same as function
overloading. Looks like the door is still open.
Regards,
Anton
On Sun,
On 12/16/18 11:33 AM, Anton Shen wrote:
Thanks for the thoughts. The part I'm missing is that why procedures
with OUT param 'will not be called from SQL environments'?
Pretty sure Pavel was referring to:
https://www.postgresql.org/docs/11/xfunc-sql.html#XFUNC-OUTPUT-PARAMETERS
"Notice that
ne 16. 12. 2018 v 20:33 odesílatel Anton Shen <4175geo...@gmail.com> napsal:
> Thanks for the thoughts. The part I'm missing is that why procedures with
> OUT param 'will not be called from SQL environments'?
>
PostgreSQL, Oracle has function/procedure overloading. The function
signature - that
Thanks for the thoughts. The part I'm missing is that why procedures with
OUT param 'will not be called from SQL environments'?
Thanks,
Anton
On Sat, Dec 15, 2018 at 10:03 AM Pavel Stehule
wrote:
> Hi
>
> út 11. 12. 2018 v 7:20 odesílatel Anton Shen <4175geo...@gmail.com>
> napsal:
>
>> Hi
Hi
út 11. 12. 2018 v 7:20 odesílatel Anton Shen <4175geo...@gmail.com> napsal:
> Hi all,
>
> I was playing around with the stored procedure support in v11 and found
> that pure OUT parameters are not supported. Is there any reason we only
> support INOUT but not OUT parameters?
>
The procedure
Hi all,
I was playing around with the stored procedure support in v11 and found
that pure OUT parameters are not supported. Is there any reason we only
support INOUT but not OUT parameters?
psql (11.0 (Homebrew petere/postgresql))
dev=# CREATE PROCEDURE test_sp(a OUT int) LANGUAGE plpgsql AS $$
