Re: [HACKERS] Re: proposal - using names as primary names of plpgsql function parameters instead $ based names

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [HACKERS] Re: proposal - using names as primary names of plpgsql function parameters instead $ based names
Дата
Msg-id 2214.1505161681@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [HACKERS] Re: proposal - using names as primary names of plpgsqlfunction parameters instead $ based names  (Jeevan Chalke <jeevan.chalke@enterprisedb.com>)
Ответы Re: [HACKERS] Re: proposal - using names as primary names of plpgsqlfunction parameters instead $ based names  (Pavel Stehule <pavel.stehule@gmail.com>)
Список pgsql-hackers
Дерево обсуждения 
Jeevan Chalke <jeevan.chalke@enterprisedb.com> writes:
[ psql-named-arguments-03-jeevan.patch ]

Pushed with minor simplification of the test case.

I'm not quite as convinced as Pavel that this is an improvement ---
it will make error messages inconsistent between named and unnamed
arguments.  Still, I follow the point that when there are a lot of
arguments, $n is pretty unhelpful.  We can always revert this if
we get complaints.
        regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: [HACKERS] More flexible LDAP auth search filters?
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: [HACKERS] Coverage improvements of src/bin/pg_basebackup andpg_receivewal --endpos