Re: CALL versus procedures with output-only arguments - Mailing list pgsql-hackers

From Tom Lane
Subject Re: CALL versus procedures with output-only arguments
Date
Msg-id 2721904.1622492719@sss.pgh.pa.us
Whole thread Raw
In response to Re: CALL versus procedures with output-only arguments  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: CALL versus procedures with output-only arguments
Re: CALL versus procedures with output-only arguments
List pgsql-hackers
I wrote:
> Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
>> I don't see that.

> It's under CREATE PROCEDURE.  11.60 <SQL-invoked routine> SR 20 says

Oh... just noticed something else relevant to this discussion: SR 13
in the same section saith

  13) If R is an SQL-invoked function, then no <SQL parameter declaration>
  in NPL shall contain a <parameter mode>.

In other words, the spec does not have OUT or INOUT parameters for
functions.  So, again, their notion of what is sufficient to identify
a routine is based on a very different model than what we are using.  

            regards, tom lane



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: storing an explicit nonce
Next
From: Noah Misch
Date:
Subject: Re: Allowing to create LEAKPROOF functions to non-superuser