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

From Petr Jelinek
Subject Re: proposal: disallow operator "=>" and use it for named parameters
Date
Msg-id [email protected]
Whole thread Raw
In response to Re: proposal: disallow operator "=>" and use it for named parameters  (Pavel Stehule <[email protected]>)
Responses Re: proposal: disallow operator "=>" and use it for named parameters
List pgsql-hackers
On 10/03/15 17:01, Pavel Stehule wrote:
>
>
> 2015-03-10 16:50 GMT+01:00 Tom Lane <[email protected]
> <mailto:[email protected]>>:
>
>     Robert Haas <[email protected] <mailto:[email protected]>>
>     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.

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



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: disallow operator "=>" and use it for named parameters
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: searching in array function - array_position