| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(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 17:44:49 |
| Message-ID: | 2370085.1927956.1426009489488.JavaMail.yahoo@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Tue, Mar 10, 2015 at 11:50 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-03-10 18:02:47 | Re: proposal: disallow operator "=>" and use it for named parameters |
| Previous Message | Tom Lane | 2015-03-10 17:12:54 | Re: Precedence of standard comparison operators |