Re: [HACKERS] Re: proposal - using names as primary names of plpgsqlfunction parameters instead $ based names
| От | Peter Eisentraut |
|---|---|
| Тема | Re: [HACKERS] Re: proposal - using names as primary names of plpgsqlfunction parameters instead $ based names |
| Дата | |
| Msg-id | 0cf239aa-91f0-b7ef-9a71-800b3ba1aa1a@2ndquadrant.com обсуждение исходный текст |
| Ответ на | [HACKERS] Re: proposal - using names as primary names of plpgsql functionparameters instead $ based names (Pavel Stehule <pavel.stehule@gmail.com>) |
| Ответы |
Re: [HACKERS] Re: proposal - using names as primary names of plpgsqlfunction parameters instead $ based names
|
| Список | pgsql-hackers |
On 5/15/17 14:34, Pavel Stehule wrote: > Now, I when I working on plpgsql_check, I have to check function > parameters. I can use fn_vargargnos and out_param_varno for list of > arguments and related varno(s). when I detect some issue, I am using > refname. It is not too nice now, because these refnames are $ based. > Long names are alias only. There are not a possibility to find > related alias. > > So, my proposal. Now, we can use names as refname of parameter > variable. $ based name can be used as alias. From user perspective > there are not any change. > > Comments, notes? > > here is a patch I don't understand what this is changing. There are not documentation or test changes. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: