| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu>, Josh Berkus <josh(at)agliodbs(dot)com>, Merlin Moncure <mmoncure(at)gmail(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 22:16:36 |
| Message-ID: | BE0F10AF-F691-4F3E-B364-573E14417E74@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Nov 15, 2013, at 2:02 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> Yeah, it would be a total foot gun here I think.
>
> I've come to the conclusion that the only possible solution is to have a separate type. That's a bit sad, but there it is. The upside is that this will make the work Teodor has mentioned simpler. (Desperately making lemonade from lemons here.)
Fine. My bikeshedding: Call the new type "jsonb". “B” for “binary.” Also, the old one is implicitly "jsona". Get it?
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2013-11-15 22:16:52 | Re: Review:Patch: SSL: prefer server cipher order |
| Previous Message | Andrew Dunstan | 2013-11-15 22:02:12 | Re: additional json functionality |