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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Petr Jelinek <petr(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: disallow operator "=>" and use it for named parameters
Date: 2015-03-10 15:12:40
Message-ID: CA+TgmoZPAuibVJa64-Z--UgfEaMXetG5wA3rSUrAvcuz1+mOzg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 19, 2015 at 3:15 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> I am marking this as Ready For Committer, the patch is trivial and works
>> as expected, there is nothing to be added to it IMHO.
>>
>> The "=>" operator was deprecated for several years so it should not be too
>> controversial either.

Committed with a few documentation tweaks.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2015-03-10 15:12:52 Re: Reduce pinning in btree indexes
Previous Message Robert Haas 2015-03-10 14:30:30 Re: proposal: searching in array function - array_position