Re: implicit vs. explicit RETURN when OUT is used

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: implicit vs. explicit RETURN when OUT is used
Дата
Msg-id 15859.1199605637@sss.pgh.pa.us
обсуждение исходный текст
Ответ на implicit vs. explicit RETURN when OUT is used  (Ivan Sergio Borgonovo <mail@webthatworks.it>)
Ответы Re: implicit vs. explicit RETURN when OUT is used  (Ivan Sergio Borgonovo <mail@webthatworks.it>)
Список pgsql-general
Ivan Sergio Borgonovo <mail@webthatworks.it> writes:
> But when I switch to
> select into _BasketID1,_BasketID2 _BasketID1,_BasketID2 from testA();
> nothing get back from testB().

I think you've forgotten that plpgsql variables will be substituted
for, wherever they appear.  The above is just an extremely expensive
form of
    _BasketID1 := _BasketID1;
    _BasketID2 := _BasketID2;
ie, a big no-op.

The general rule of thumb is not to name plpgsql parameters or variables
the same as fields you'll need to reference in the queries in the
function.

            regards, tom lane

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

Предыдущее
От: "Scott Marlowe"
Дата:
Сообщение: Re: Performance problem. Could it be related to 8.3-beta4?
Следующее
От: Ivan Sergio Borgonovo
Дата:
Сообщение: Re: implicit vs. explicit RETURN when OUT is used