Re: a column definition list is required for functions returning "record" - Mailing list pgsql-general

From Jim Nasby
Subject Re: a column definition list is required for functions returning "record"
Date
Msg-id c9977874-bf65-97bd-9e23-8533a59e8d8f@BlueTreble.com
Whole thread Raw
In response to Re: a column definition list is required for functions returning "record"  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: a column definition list is required for functions returning "record"
List 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


pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: How to assemble all fields of (any) view into a string?
Next
From: Ken Tanzer
Date:
Subject: Re: How to assemble all fields of (any) view into a string?