From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com> |
Cc: | 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 18:34:20 |
Message-ID: | CA+U5nMJ5OJCKGqOc2sovtvLo=WtvkTmKSD4iC6nuBg=pXCfNKA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
> * 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.
Lets JFDI
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | pratikchirania | 2011-12-15 18:42:03 | Re: pgstat wait timeout |
Previous Message | Tomas Vondra | 2011-12-15 18:34:13 | Re: pgstat wait timeout |