| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Claes Jakobsson <claes(at)gluefinance(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>, Jan Wieck <janwieck(at)yahoo(dot)com> |
| Subject: | Re: JSON for PG 9.2 |
| Date: | 2011-12-18 03:46:03 |
| Message-ID: | CA+Tgmoan+--uYR59Yc3N9R3a8kSxZMpHcNX6y6a88Xnmh--_Pw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Dec 17, 2011 at 10:42 PM, David E. Wheeler <david(at)kineticode(dot)com> wrote:
> On Dec 17, 2011, at 7:40 PM, Tom Lane wrote:
>> Well, I think that that's exactly the question here: if we do something
>> in core, will it foreclose options for people who want to do add-ons?
>
> Why would it? They would just have to use a different name.
Yeah, exactly. Or for that matter, the same name in a different
schema. And as for the question of text vs. binary, that's going to
be two separate data types whether it gets done in core or elsewhere.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-12-18 04:09:39 | Re: Allow substitute allocators for PGresult. |
| Previous Message | David E. Wheeler | 2011-12-18 03:42:09 | Re: JSON for PG 9.2 |