Re: Support for OUT parameters in procedures

From: Robert Haas <robertmhaas(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: Support for OUT parameters in procedures
Date: 2020-08-27 13:56:47
Message-ID: CA+TgmobV5QdvDq7LJbRYULi9U7dUQnYz8MzhVmgMrDUmEUV4VQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

On Thu, Aug 27, 2020 at 4:34 AM Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> For a top-level direct call, you can pass whatever you want, since all
> OUT parameters are presented as initially NULL to the procedure code.
> So you could just pass NULL, as in CALL test_proc(5, NULL).

Is that actually how other systems work? I would think that people
would expect to pass, say, a package variable, and expect that it will
get updated.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-08-27 14:04:04 Re: factorial function/phase out postfix operators?
Previous Message Stephen Frost 2020-08-27 13:55:33 Re: [EXTERNAL] Re: WIP: WAL prefetch (another approach)

Browse pgsql-jdbc by date

  From Date Subject
Next Message Peter Eisentraut 2020-08-28 06:04:04 Re: Support for OUT parameters in procedures
Previous Message Jason Breitman 2020-08-27 13:05:56 Re: GSSAPI Authentication using a CNAME