Re: proposal: disallow operator "=>" and use it for named parameters
От | Pavel Stehule |
---|---|
Тема | Re: proposal: disallow operator "=>" and use it for named parameters |
Дата | |
Msg-id | CAFj8pRCXbvBeHxY88+OkkxcK8+t_Sd4k96kQqRCABtDtrYXKtg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: proposal: disallow operator "=>" and use it for named parameters (Robert Haas <robertmhaas@gmail.com>) |
Список | pgsql-hackers |
2015-01-19 4:54 GMT+01:00 Robert Haas <robertmhaas@gmail.com>:
On Sat, Jan 17, 2015 at 8:27 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> two years a operator "=>" is marked as deprecated (from PostgreSQL 9.2).
>
> Isn't time to use it for named parameters now (for PostgreSQL 9.5) ?
I'm cool with that. It's possible that there are installations out
there that still have => operators installed, but every
still-supported release warns you not to do that, and the hstore
change exists in three released versions. Anyway, no amount of
waiting will eliminate the hazard completely.
> I am sending a implementation where syntax based on "=>" symbol is second
> (but preferred) variant of ":=" syntax .. syntax ":=" will be supported
> still.
>
> Here is a patch
I think you should just remove the WARNING, not change it to an error.
If somebody wants to quote the operator name to be able to continue
using it, I think that's OK.
I have no problem with it. Just I'll try if there are no some unexpected problem and I'll send a updated patch
Regards
Pavel
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: