Re: plpgsql + named parameters

Поиск
Список
Период
Сортировка
Искать
От
Steve Prentice
Тема
Re: plpgsql + named parameters
Дата
в 13:58:09
Msg-id
23DAA99A-B116-4EEE-A64A-AE95047B70F9@cisco.com
Ответ на
Список
Дерево обсуждения
plpgsql + named parameters Steve Prentice <prentice@cisco.com>
Re: plpgsql + named parameters Merlin Moncure <mmoncure@gmail.com>
Re: plpgsql + named parameters Steve Prentice <prentice@cisco.com>
Re: plpgsql + named parameters Pavel Stehule <pavel.stehule@gmail.com>
Re: plpgsql + named parameters Steve Prentice <prentice@cisco.com>
Re: plpgsql + named parameters Pavel Stehule <pavel.stehule@gmail.com>
       t := fun1(1 as a);      -- syntax error: "SELECT  fun1(1 as  $1 )"
       t := fun1(a as a);      -- syntax error: "SELECT  fun1( $1  as  $1 )"

On May 19, 2009, at 6:42 PM, Merlin Moncure wrote:
you have a name conflict here...is it deliberate? I've learned the
hard way to always, always prefix arguments and locals to plpgsql
functions with '_'.  Or are you trying to do something fancier?

The conflict is deliberate to illustrate the limitations the named parameter feature (on the list for the first 8.5 CommitFest) is going to have if parameter substitution is not addressed at the same time.

-Steve
В списке pgsql-hackers по дате отправления
От: Dimitri Fontaine
Дата:
От: Pavel Stehule
Дата:
Сообщение: Re: plpgsql + named parameters
FAQ