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

From Pavel Stehule
Subject Re: proposal: disallow operator "=>" and use it for named parameters
Date
Msg-id CAFj8pRBKc0c2uKOnuetxLWFRrEbDkcu=11qL7B7bM4uqxrR=Rg@mail.gmail.com
Whole thread Raw
In response to Re: proposal: disallow operator "=>" and use it for named parameters  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: proposal: disallow operator "=>" and use it for named parameters
List pgsql-hackers


2015-01-19 14:27 GMT+01:00 Robert Haas <robertmhaas@gmail.com>:
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.

yes, I removed it

Regards

Pavel
 

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

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] explain sortorder
Next
From: Tom Lane
Date:
Subject: Re: Re: Better way of dealing with pgstat wait timeout during buildfarm runs?