| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, "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:57:14 |
| Message-ID: | 20131115205714.GK5489@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-11-15 12:54:53 -0800, Josh Berkus 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.
It's also not currently possible to implement such a behaviour inside a
type's functions. You'd need core code cooperation.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | J Smith | 2013-11-15 21:01:07 | Re: Errors on missing pg_subtrans/ files with 9.3 |
| Previous Message | Merlin Moncure | 2013-11-15 20:56:54 | Re: additional json functionality |