| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: disallow operator "=>" and use it for named parameters |
| Date: | 2015-01-19 13:27:20 |
| Message-ID: | CA+TgmoaRDf_kDULnHoxE7dCKWoOQx+di2fR-Fb9kkuMMMTt7Fw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 19, 2015 at 2:59 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-01-19 13:30:11 | Re: proposal: disallow operator "=>" and use it for named parameters |
| Previous Message | Stephen Frost | 2015-01-19 13:26:59 | Re: pgaudit - an auditing extension for PostgreSQL |