Re: additional json functionality - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: additional json functionality
Date
Msg-id C4D17E63-F7BD-4A3F-9B29-AE28788EC8B4@justatheory.com
Whole thread Raw
In response to Re: additional json functionality  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: additional json functionality  (Garick Hamlin <ghamlin@isc.upenn.edu>)
List pgsql-hackers
On Nov 13, 2013, at 4:45 PM, Andrew Dunstan <andrew@dunslane.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
stufforder will be destroyed and not stored anywhere, and duplicate keys will be lost. Once that's done, how would a
prettyprint option restore the lost info? 

I meant ordering the keys, usually in lexicographic order. I agree that preserving order is untenable.

Best,

David


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: additional json functionality
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH] pg_basebackup: progress report max once per second