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

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Petr Jelinek <petr(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-03-10 16:14:39
Message-ID: CAFj8pRDy7maag26GuCqKONqfv8DqihKDgiXWiAaWwL-B_NtD7Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2015-03-10 17:07 GMT+01:00 Petr Jelinek <petr(at)2ndquadrant(dot)com>:

> On 10/03/15 17:01, Pavel Stehule wrote:
>
>>
>>
>> 2015-03-10 16:50 GMT+01:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us
>> <mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>>:
>>
>> Robert Haas <robertmhaas(at)gmail(dot)com <mailto:robertmhaas(at)gmail(dot)com>>
>> writes:
>>
>> > Committed with a few documentation tweaks.
>>
>> Was there any consideration given to whether ruleutils should start
>> printing NamedArgExprs with "=>"? Or do we think that needs to wait?
>>
>>
>> I didn't think about it? I don't see any reason why it have to use
>> deprecated syntax.
>>
>>
> There is one, loading the output into older version of Postgres. Don't
> know if that's important one though.

I don't think so it is a hard issue. We doesn't support downgrades - and if
somebody needs it, it can fix it with some regexp. We should to use
preferred syntax everywhere - and preferred syntax should be ANSI.

I forgot it :(

Pavel

>
>
> --
> Petr Jelinek http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-03-10 16:29:33 Re: Precedence of standard comparison operators
Previous Message Tom Lane 2015-03-10 16:11:57 Re: Precedence of standard comparison operators