| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: row_to_array function |
| Date: | 2015-06-23 21:50:07 |
| Message-ID: | CAHyXU0xrk4FdxfAtFPwyKhtU+==aNyN-5sshEx6z7wLbEn_T8g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 23, 2015 at 3:45 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> On 6/23/15 3:22 PM, Merlin Moncure wrote:
>>
>> I would rephrase that to: "do X to all fields of an object".
>> Array handling is pretty good now (minus arrays of arrays, but arrays
>
>
> Except that still won't make it easy to do something to each element of an
> array in SQL, which I think would be nice to have.
Maybe, or maybe we're framing the problem incorrectly. To me, it's
not really all that difficult to do:
select foo(x) from unnest(bar) x;
Unless you have to maintain state inside of foo(), in which case I'd
probably using the highly underutilized 'window over custom aggregate'
technique.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-06-23 23:44:36 | Oh, this is embarrassing: init file logic is still broken |
| Previous Message | Kevin Grittner | 2015-06-23 21:48:44 | Re: 9.5 release notes |