Re: Out parameters handling
От | Tom Lane |
---|---|
Тема | Re: Out parameters handling |
Дата | |
Msg-id | 14100.1236443574@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Out parameters handling (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Out parameters handling
Re: Out parameters handling Re: Out parameters handling Re: Out parameters handling |
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > On Sat, Mar 7, 2009 at 9:08 AM, Rod Taylor <rod.taylor@gmail.com> wrote: >> It wouldn't be so bad if you could assign internal and external column names. > This is a good point. Uglifying the parameter names is sort of OK for > input parameters, but is much more annoying for output parameters. How much of this pain would go away if we changed over to the arguably correct (as in Or*cle does it that way) scoping for names, wherein the parser first tries to match a name against column names of tables of the current SQL statement, and only failing that looks to see if they are plpgsql variables? regards, tom lane
В списке pgsql-hackers по дате отправления: