| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | David Fetter <david(at)fetter(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Joseph Adams <joeyadams3(dot)14159(at)gmail(dot)com>, 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 23:47:37 |
| Message-ID: | 201008112347.o7BNlbG02342@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan wrote:
>
>
> On 08/11/2010 07:33 PM, David Fetter wrote:
> >> I would be curious to the benefit of putting it in core. I have no
> >> problem with the type but in core?
> > If it's not in core, the vast majority of users will not have it
> > installed, and nothing, in core or otherwise, will be able to count on
> > it.
> >
> >
>
>
> You could say that about almost any feature. PostgreSQL is designed to
> be modular, and we can hardly credibly use that as an argument against
> ourselves.
>
> A convincing argument would be that there is another feature we want in
> core that needs or at least could benefit from it.
I would say that JSON is no longer a niche data format, which would
suggest its inclusion in core.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2010-08-11 23:49:58 | Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP) |
| Previous Message | Peter Geoghegan | 2010-08-11 23:42:15 | Re: string_to_array with an empty input string |