| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: additional json functionality |
| Date: | 2013-11-14 00:50:49 |
| Message-ID: | C4D17E63-F7BD-4A3F-9B29-AE28788EC8B4@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Nov 13, 2013, at 4:45 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> It should be a pretty-printing function option, perhaps, but not core to the type itself, IMO.
>
> I don't in the least understand how it could be a pretty printing option. If we move to a binary rep using the hstore stuff order will be destroyed and not stored anywhere, and duplicate keys will be lost. Once that's done, how would a pretty print option restore the lost info?
I meant ordering the keys, usually in lexicographic order. I agree that preserving order is untenable.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2013-11-14 01:51:52 | Re: [PATCH] pg_basebackup: progress report max once per second |
| Previous Message | Andrew Dunstan | 2013-11-14 00:45:26 | Re: additional json functionality |