Re: proposal: disallow operator "=>" and use it for named parameters

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: disallow operator "=>" and use it for named parameters
Date: 2015-01-19 16:03:18
Message-ID: CAFj8pRBZOvebbYHKzqv6-h0HFi04N0wf8HekRL5ztg3do2zHgw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2015-01-19 14:30 GMT+01:00 Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>:

> Pavel Stehule wrote:
>
> > 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 "=>" (
> > + ^
>
> Does it work to use OPERATOR(=>) syntax? I don't think identifier
> quoting works for operators.
>

it doesn't work too

>
> --
> Álvaro Herrera http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2015-01-19 16:05:22 Re: WITH CHECK and Column-Level Privileges
Previous Message Robert Haas 2015-01-19 16:01:11 Re: Re: Better way of dealing with pgstat wait timeout during buildfarm runs?