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

From Kevin Grittner
Subject Re: proposal: disallow operator "=>" and use it for named parameters
Date
Msg-id 2370085.1927956.1426009489488.JavaMail.yahoo@mail.yahoo.com
Whole thread Raw
In response to Re: proposal: disallow operator "=>" and use it for named parameters  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: proposal: disallow operator "=>" and use it for named parameters
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Tue, Mar 10, 2015 at 11:50 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Was there any consideration given to whether ruleutils should start
>>> printing NamedArgExprs with "=>"?  Or do we think that needs to wait?
>>
>> I have to admit that I didn't consider that.  What do you think?  I
>> guess I'd be tentatively in favor of changing that to match, but I
>> could be convinced otherwise.

> Presumably we are going to change it at some point; maybe we
> should just do it rather than waiting another 5 years.

+1

It has been deprecated long enough that I don't see the point of waiting.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Precedence of standard comparison operators
Next
From: Tom Lane
Date:
Subject: Re: proposal: disallow operator "=>" and use it for named parameters