| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
| 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:45:26 |
| Message-ID: | 52841D26.5040507@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/13/2013 07:39 PM, David E. Wheeler wrote:
> On Nov 13, 2013, at 2:41 PM, Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> wrote:
>
>> Would be possible to have a boolean, such as 'strict' - so that unique & ordered was only imposed when strict was TRUE? Alternately, separate functions to allow the same choice?
> 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?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2013-11-14 00:50:49 | Re: additional json functionality |
| Previous Message | Tatsuo Ishii | 2013-11-14 00:43:04 | Re: UTF8 national character data type support WIP patch and list of open issues. |