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

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: proposal: disallow operator "=>" and use it for named parameters
Дата
Msg-id CA+TgmoYH8b6tanF-V5_U1-edbvvB8breGPUXWRQj_8rJbP38LA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: proposal: disallow operator "=>" and use it for named parameters  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: proposal: disallow operator "=>" and use it for named parameters  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Tue, Mar 10, 2015 at 11:50 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Thu, Feb 19, 2015 at 3:15 PM, Pavel Stehule <pavel.stehule@gmail.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.
>
> 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.

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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Precedence of standard comparison operators
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Precedence of standard comparison operators