From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: JSON for PG 9.2 |
Date: | 2011-12-15 21:47:30 |
Message-ID: | 4EEA6AF2.3090707@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/15/2011 01:34 PM, Simon Riggs wrote:
> On Tue, Dec 13, 2011 at 8:15 AM, Joey Adams<joeyadams3(dot)14159(at)gmail(dot)com> wrote:
>
>> Issues we've encountered include:
>>
>> * Should JSON be stored as binary or as text?
> Text
Works for me.
>> * How do we deal with Unicode escapes and characters if the server or
>> client encoding is not UTF-8? Some (common!) character encodings have
>> code points that don't map to Unicode. Also, the charset conversion
>> modules do not provide fast entry points for converting individual
>> characters; each conversion involves a funcapi call.
> Make JSON datatypes only selectable if client encoding is UTF-8.
Yuck. Do we have this sort of restriction for any other data type?
ISTM that the encoding problem is at least as likely to be the reverse
of what's above - i.e. that there's a code point in the stored JSON
that's not represented in the client encoding.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | amit sehas | 2011-12-15 22:15:53 | array behavior |
Previous Message | amit sehas | 2011-12-15 21:15:57 | Cursor behavior |