Jim Nasby writes:
> Let me ask a related question: is there any reason why we don't accept
> argument names or the default specifier in the regprocedure cast?
regprocedure_in does not contain a full SQL parser, which it would pretty
much need in order to deal with default expressions. Argument
On 5/6/14, 1:57 PM, Peter Eisentraut wrote:
On 5/5/14, 4:09 PM, Jim Nasby wrote:
They do not accept DEFAULT though:
GRANT EXECUTE ON FUNCTION test(t text DEFAULT '') to public;
ERROR: syntax error at or near "DEFAULT"
LINE 1: GRANT EXECUTE ON FUNCTION test(t text DEFAULT '') to public;
Presum
On 5/5/14, 3:22 PM, Alvaro Herrera wrote:
> Jim Nasby wrote:
>> Prior to default parameters on functions, GRANT and COMMENT accepted full
>> parameter syntax. IE:
>>
>> GRANT EXECUTE ON test(t text) TO public
>>
>> as opposed to regprocedure, which only accepts the data types ( test(text),
On 5/5/14, 4:09 PM, Jim Nasby wrote:
> They do not accept DEFAULT though:
>
> GRANT EXECUTE ON FUNCTION test(t text DEFAULT '') to public;
> ERROR: syntax error at or near "DEFAULT"
> LINE 1: GRANT EXECUTE ON FUNCTION test(t text DEFAULT '') to public;
>
> Presumably this is just an oversight?
Jim Nasby wrote:
> Prior to default parameters on functions, GRANT and COMMENT accepted full
> parameter syntax. IE:
>
> GRANT EXECUTE ON test(t text) TO public
>
> as opposed to regprocedure, which only accepts the data types ( test(text),
> not test(t text) ).
>
> They do not accept DEFAULT
Prior to default parameters on functions, GRANT and COMMENT accepted full
parameter syntax. IE:
GRANT EXECUTE ON test(t text) TO public
as opposed to regprocedure, which only accepts the data types ( test(text), not
test(t text) ).
They do not accept DEFAULT though:
GRANT EXECUTE ON FUNCTION