Re: proposal: row_to_array function - Mailing list pgsql-hackers

From Tom Lane
Subject Re: proposal: row_to_array function
Date
Msg-id 25419.1427653646@sss.pgh.pa.us
Whole thread Raw
In response to Re: proposal: row_to_array function  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: proposal: row_to_array function  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: proposal: row_to_array function  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
Pavel Stehule <pavel.stehule@gmail.com> writes:
> here is rebased patch.
> It contains both patches - row_to_array function and foreach array support.

While I don't have a problem with hstore_to_array, I don't think that
row_to_array is a very good idea; it's basically encouraging people to
throw away SQL datatypes altogether and imagine that everything is text.
They've already bought into that concept if they are using hstore or
json, so smashing elements of those containers to text is not a problem.
But that doesn't make this version a good thing.

(In any case, those who insist can get there through row_to_json, no?)

Also, could we please *not* mix up these two very independent features?
"foreach array" as implemented here may or may not be a good thing, but
it should get its own discussion.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: extend pgbench expressions with functions
Next
From: Fabien COELHO
Date:
Subject: Re: getting rid of "thread fork emulation" in pgbench?