| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: additional json functionality |
| Date: | 2013-11-15 20:56:54 |
| Message-ID: | CAHyXU0yTAGQvQURVXWaPnMO+zZOHMgvTUbe4f54D3Df2ERHRzQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 15, 2013 at 2:54 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 11/15/2013 12:25 PM, Merlin Moncure wrote:
>> Kinda yes, kinda no. Here's a rough sketch of what I'm thinking:
>>
>> *) 'json' type internally has a binary as well a text representation.
>> The text representation is basically the current type behavior
>
> <snip long detailed explanation of behavior-dependant type>
>
> That's not at all workable. Users would be completely unable to predict
> or understand the JSON type and how it acts. That's not just violating
> POLS; that's bashing POLS' head in with a shovel.
All right: make a new type then, and leave the current one alone please.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-11-15 20:57:14 | Re: additional json functionality |
| Previous Message | Josh Berkus | 2013-11-15 20:54:53 | Re: additional json functionality |