| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Alexander Farber <alexander(dot)farber(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: a column definition list is required for functions returning "record" |
| Date: | 2016-09-07 22:27:09 |
| Message-ID: | c9977874-bf65-97bd-9e23-8533a59e8d8f@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 9/7/16 2:02 PM, Merlin Moncure wrote:
>>> >> Exactly. You can pass anonymous record types around today, as long as you
>>> >> don't do anything that requires knowing what their contents are, either in
>>> >> the function or in the calling query:
>> >
>> > What I was thinking of is something (like a function) that has explicitly
>> > defined what the contents of the record are.
> We have that already, it's named 'json_each_text'
Apparently you haven't looked at json parse/deparse costs ;P
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ken Tanzer | 2016-09-07 22:32:10 | Re: How to assemble all fields of (any) view into a string? |
| Previous Message | Adrian Klaver | 2016-09-07 22:18:35 | Re: How to assemble all fields of (any) view into a string? |