Re: CALL versus procedures with output-only arguments
От | Tom Lane |
---|---|
Тема | Re: CALL versus procedures with output-only arguments |
Дата | |
Msg-id | 2721904.1622492719@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: CALL versus procedures with output-only arguments (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: CALL versus procedures with output-only arguments
Re: CALL versus procedures with output-only arguments |
Список | 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 по дате отправления: