Re: RETURNING MORE THAN ONE CUSTOM TYPE FROM FUNCTION

Поиск
Список
Период
Сортировка
От Merlin Moncure
Тема Re: RETURNING MORE THAN ONE CUSTOM TYPE FROM FUNCTION
Дата
Msg-id CAHyXU0yjhxANPPsgztwwUGhnyg6Re9Sazr4nmLXOmL+fjCtjEQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: RETURNING MORE THAN ONE CUSTOM TYPE FROM FUNCTION  (utsav <utsav.pshah@tcs.com>)
Ответы Re: RETURNING MORE THAN ONE CUSTOM TYPE FROM FUNCTION  (utsav <utsav.pshah@tcs.com>)
Re: RETURNING MORE THAN ONE CUSTOM TYPE FROM FUNCTION  (utsav <utsav.pshah@tcs.com>)
Список pgsql-general
On Mon, Jun 18, 2012 at 4:30 AM, utsav <utsav.pshah@tcs.com> wrote:
> Thanks for reply but you have used SQL as a language .
>
> Please give me Plpgsql example because  i am facing problem in plpgsql only

create function f(foo out foo, bar out bar) returns setof
record as $$
begin
 return query select (v, v::text)::foo, (v, v::text)::bar from
generate_series(1,3) v;
end
$$ language plpgsql;

 -- or --

create or replace function f(foo out foo, bar out bar) returns setof
record as $$
begin
 f.foo = (1,'a')::foo;
 f.bar = (2,'b')::bar;
 return next;
end
$$ language plpgsql;

(in older versions of postgres you might have to be a little more
careful about names of input and output arguments).

merlin

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

Предыдущее
От: Sergey Konoplev
Дата:
Сообщение: Re: array vs bit fields for masking
Следующее
От: Stefan Schwarzer
Дата:
Сообщение: How to include Tablefunc as an extension