From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Joseph Adams <joeyadams3(dot)14159(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP) |
Date: | 2010-08-11 08:24:45 |
Message-ID: | 1281515085.2142.1486.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, 2010-07-24 at 18:57 -0400, Joseph Adams wrote:
> I've been developing it as a contrib module because:
> * I'd imagine it's easier than developing it as a built-in datatype
> right away (e.g. editing a .sql.in file versus editing pg_type.h ).
> * As a module, it has PGXS support, so people can try it out right
> away rather than having to recompile PostgreSQL.
>
> I, for one, think it would be great if the JSON datatype were all in
> core :-) However, if and how much JSON code should go into core is up
> for discussion. Thoughts, anyone?
As a GSoC piece of work, doing it as a contrib module gives an
immediately useful deliverable. Good plan.
Once that is available, we can then get some feedback on it and include
it as an in-core datatype later in the 9.1 cycle.
So lets do both: contrib and in-core.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2010-08-11 08:26:55 | Re: trace_recovery_messages |
Previous Message | Boxuan Zhai | 2010-08-11 08:11:24 | Re: MERGE Specification |