| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | "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:39:37 |
| Message-ID: | 4C6334B9.3080001@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2010-08-11 23:42:15 | Re: string_to_array with an empty input string |
| Previous Message | David Fetter | 2010-08-11 23:33:37 | Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP) |