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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <kgrittn(at)ymail(dot)com>, 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 18:51:30
Message-ID: CA+TgmobCMF7F50+feJpcLR8E_Lyv45AYXBSdiog-NS7VLuFopg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 10, 2015 at 2:32 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> 1. funcname_signature_string
> 2. get_rule_expr

Thanks. Patch attached. I'll commit this if there are no objections.

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

Attachment Content-Type Size
named-expr-fixes.patch binary/octet-stream 3.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex Hunsaker 2015-03-10 19:10:03 Re: Precedence of standard comparison operators
Previous Message Tom Lane 2015-03-10 18:50:19 Re: proposal: searching in array function - array_position