Re: proposal: disallow operator "=>" and use it for named parameters - Mailing list pgsql-hackers

From Robert Haas
Subject Re: proposal: disallow operator "=>" and use it for named parameters
Date
Msg-id CA+TgmoaRDf_kDULnHoxE7dCKWoOQx+di2fR-Fb9kkuMMMTt7Fw@mail.gmail.com
Whole thread Raw
In response to Re: proposal: disallow operator "=>" and use it for named parameters  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: proposal: disallow operator "=>" and use it for named parameters
List pgsql-hackers
On Mon, Jan 19, 2015 at 2:59 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>> I think you should just remove the WARNING, not change it to an error.
>> If somebody wants to quote the operator name to be able to continue
>> using it, I think that's OK.
>
> It looks so quoting doesn't help here
>
> + CREATE OPERATOR "=>" (
> +    leftarg = int8,<--><------>-- right unary
> +    procedure = numeric_fac
> + );
> + ERROR:  syntax error at or near "("
> + LINE 1: CREATE OPERATOR "=>" (
> +                              ^

Well then the error check is just dead code.  Either way, you don't need it.

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



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: pgaudit - an auditing extension for PostgreSQL
Next
From: Alvaro Herrera
Date:
Subject: Re: proposal: disallow operator "=>" and use it for named parameters