Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: [HACKERS] Re: proposal - using names as primary names of plpgsql function parameters instead $ based names
Date
Msg-id 2214.1505161681@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Re: proposal - using names as primary names of plpgsqlfunction parameters instead $ based names  (Jeevan Chalke <jeevan.chalke@enterprisedb.com>)
Responses Re: [HACKERS] Re: proposal - using names as primary names of plpgsqlfunction parameters instead $ based names
List pgsql-hackers
Tree view 
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 by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] More flexible LDAP auth search filters?
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Coverage improvements of src/bin/pg_basebackup andpg_receivewal --endpos