Fri, Sep 2, 2016 at 6:55 PM, Jim Nasby <Jim.Nasby@xxxxxxxxxxxxxx> wrote: > On 8/29/16 6:28 AM, Tom Lane wrote: >> >> Pavel Stehule <pavel.stehule@xxxxxxxxx> writes: >>> >>> > 2016-08-29 1:59 GMT+02:00 Jim Nasby <Jim.Nasby@xxxxxxxxxxxxxx>: >>>> >>>> >> It would be nice if there was a way to pass dynamically formed >>>> >> records >>>> >> around, similar to how you can pass the results of row() around. >>>> >> Someone >>>> >> else has actually be asking about this at >>>> >> https://github.com/decibel/pg_ >>>> >> lambda/issues/1. >>> >>> > Probably there is a space to be PLpgSQL more flexible - but there are >>> > limits - PLpgSQL is black box for SQL engine, and when output is any >>> > record >>> > type, then SQL engine knows zero about returning data structure in >>> > preprocessing time. >> >> 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' :-). merlin -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
