Re: counterintuitive behaviour in pl/pgsql

Поиск
Список
Период
Сортировка
От Michael Glaesemann
Тема Re: counterintuitive behaviour in pl/pgsql
Дата
Msg-id 52D6BAD5-5A1C-4009-82DE-A9FFDD35E2EC@seespotcode.net
обсуждение исходный текст
Ответ на Re: counterintuitive behaviour in pl/pgsql  (Pavel Stehule <pavel.stehule@gmail.com>)
Список pgsql-general
On May 21, 2011, at 13:44, Pavel Stehule wrote:

> 2011/5/21 Michael Glaesemann <grzm@seespotcode.net>:
>>
>> It looks like it's just column names stomping on variable names, which is a known issue. This is why a lot of
developers(including myself) have conventions of prefixing parameters and variable names (I use in_ for input
parameters,v_ for internally defined variables). 
>>
>
> It is not this case. There is two plpgsql variables with same name in
> one namespace - the last OUT variable has higher priority.

Yeah, I see that now (after seeing Tom's post). Thanks for the confirmation.

Michael Glaesemann
grzm seespotcode net




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

Предыдущее
От: Ben Chobot
Дата:
Сообщение: Re: understanding pg_locks
Следующее
От: jun yang
Дата:
Сообщение: how to start a procedure after postgresql started.