Re: JSON and unicode surrogate pairs - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: JSON and unicode surrogate pairs
Date
Msg-id 51B72C28.4010606@dunslane.net
Whole thread Raw
In response to Re: JSON and unicode surrogate pairs  (Hannu Krosing <hannu@2ndQuadrant.com>)
Responses Re: JSON and unicode surrogate pairs  (Hannu Krosing <hannu@2ndQuadrant.com>)
List pgsql-hackers
On 06/11/2013 09:23 AM, Hannu Krosing wrote:

>
> I can see no possible JavaScript structure which could produce duplicate
> key when serialised.
>
> And I don't think that any standard JSON reader supports this either.

You are quite wrong. This was discussed quite recently on -hackers, too. 
V8 will happily accept a JSON string with duplicate keys via eval() and 
resolve it in favor of the lexically latest value. I gather most other 
JSON processors do likewise.


Can we PLEASE PLEASE stop sending this discussion off track and 
concentrate on the actual problem we have at hand? It's BETA and there 
is not much time. I get that you don't like how we have implemented 
JSON. But we're not going back over that ground now. It's done and in 
use and LOTS of people are finding it very useful.


cheers

andrew



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: how to find out whether a view is updatable
Next
From: Hannu Krosing
Date:
Subject: Re: JSON and unicode surrogate pairs