| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Hannu Krosing <hannu(at)2ndquadrant(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Josh Berkus <josh(at)agliodbs(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-19 16:14:37 |
| Message-ID: | CA+TgmoaERPm7YT0bxi_c1dvoz5sWGzRWzwcAFRtj0oCFhrUpFQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 14, 2013 at 2:54 PM, Hannu Krosing <hannu(at)2ndquadrant(dot)com> wrote:
> I am sure you could also devise an json encoding scheme
> where white space is significant ;)
I don't even have to think hard. If you want your JSON to be
human-readable, it's entirely possible that you want it stored using
the same whitespace that was present on input. There is a valid use
case for normalizing whitespace, too, of course.
Everyone on this thread who thinks that there is Only One Right Way To
Do It should take a chill pill. There is, in fact, more than one
right way to do it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-11-19 16:16:53 | Re: Changing pg_dump default file format |
| Previous Message | Tom Lane | 2013-11-19 16:13:26 | Re: UNNEST with multiple args, and TABLE with multiple funcs |