Re: function_name.parameter_name

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: function_name.parameter_name
Дата
Msg-id D8A5AADE-3D2D-4479-AB8F-FF6C7EDD0B02@gmail.com
обсуждение исходный текст
Ответ на Re: function_name.parameter_name  (Darren Duncan <darren@darrenduncan.net>)
Ответы Re: function_name.parameter_name  (Darren Duncan <darren@darrenduncan.net>)
Список pgsql-hackers
On Sep 8, 2010, at 3:17 PM, Darren Duncan <darren@darrenduncan.net> wrote:
> Bruce Momjian wrote:
>> Sergey Konoplev wrote:
>>> 1.
>>> CREATE FUNCTION func_name(arg_name text) RETURNS integer AS $$
>>> BEGIN
>>>    RAISE INFO '%', func_name.arg_name;
>>> ...
>>>
>>> 2.
>>> CREATE FUNCTION func_name() RETURNS integer AS $$
>>> DECLARE
>>>    var_name text := 'bla';
>>> BEGIN
>>>    RAISE INFO '%', func_name.var_name;
>>> ...
>>>
>>> 3.
>>> CREATE FUNCTION func_very_very_very_very_long_name() RETURNS integer AS $$
>>> << func_alias >>
>>> DECLARE
>>>    var_name text := 'bla';
>>> BEGIN
>>>    RAISE INFO '%', func_alias.var_name;
>>> ...
>
> I suggest that it might be reasonable to introduce a new syntax, that isn't already valid for something inside a
routine,and use that as a terse way to reference the current function and/or its parameters.  This may best be a simple
constantsyntax. 

This has been proposed in the past and Tom has rejected it, but I agree that it would be useful.  The key word in this
proposalis "terse". 

...Robert

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Postgres 9.0.0 release scheduled
Следующее
От: Darren Duncan
Дата:
Сообщение: Re: function_name.parameter_name