From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: UNNEST with multiple args, and TABLE with multiple funcs |
Date: | 2013-11-22 12:53:10 |
Message-ID: | 87eh68vbvm.fsf@news-spur.riddles.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
Tom> I've committed this patch after some significant editorialization, but
Tom> leaving the use of TABLE( ... ) syntax in-place. If we decide that we
Tom> don't want to risk doing that, we can change to some other syntax later.
Is this intended:
create function foo() returns setof footype language plpgsql
as $f$ begin return next row(1,true); end; $f$;
select pg_typeof(f), row_to_json(f) from foo() with ordinality f(p,q);
pg_typeof | row_to_json
-----------+---------------------------------
record | {"p":1,"q":true,"ordinality":1}
(1 row)
select pg_typeof(f), row_to_json(f) from foo() f(p,q);
pg_typeof | row_to_json
-----------+------------------
footype | {"a":1,"b":true}
(1 row)
--
Andrew (irc:RhodiumToad)
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2013-11-22 12:54:53 | Re: Add \i option to bring in the specified file as a quoted literal |
Previous Message | Rodolfo Campero | 2013-11-22 12:37:25 | Re: information schema parameter_default implementation |