From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: GSoC project suggestion: PIVOT ? |
Date: | 2014-03-31 04:36:17 |
Message-ID: | CAFcNs+qXDcYX7yDn0L1_+Foz+cCdAJB+p4dV70UATmdXNKTo5A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Mar 30, 2014 at 11:30 PM, Craig Ringer <craig(at)2ndquadrant(dot)com>
wrote:
>
> Hi all
>
> The thought just occurred to me that a PIVOT feature might be a
> respectable GSoC project.
>
> tablefunc/crosstab works, but it's very clumsy to use, and difficult to
> consume the data from. Going by Stack Overflow activity, pivot/crosstab
> is second only to upsert when it comes to things that users find hard to
> do in Pg.
>
> I haven't investigated what'd be involved in implementing any integrated
> form of pivoting, and I'm aware that there are some serious challenges
> when it comes to generating a TupleDesc for pivot output. I thought I'd
> raise it in case anyone has looked into this and has any comments on
> whether this'd be a viable GSoC for an interested student.
>
It's a nice idea, but the deadline to students send a proposal was 21th
April.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2014-03-31 04:49:58 | Re: GSoC project suggestion: PIVOT ? |
Previous Message | Amit Kapila | 2014-03-31 04:35:36 | Re: issue log message to suggest VACUUM FULL if a table is nearly empty |