On Tue, Jul 19, 2011 at 9:03 PM, Joey Adams <joeyadams3.14159@gmail.com> wrote:
> On Mon, Jul 18, 2011 at 7:36 PM, Florian Pflug <fgp@phlo.org> wrote:
>> On Jul19, 2011, at 00:17 , Joey Adams wrote:
>>> I suppose a simple solution would be to convert all escapes and
>>> outright ban escapes of characters not in the database encoding.
>>
>> +1. Making JSON work like TEXT when it comes to encoding issues
>> makes this all much simpler conceptually. It also avoids all kinds
>> of weird issues if you extract textual values from a JSON document
>> server-side.
>
> Thanks for the input. I'm leaning in this direction too. However, it
> will be a tad tricky to implement the conversions efficiently, ...
I'm a bit confused, because I thought what I was talking about was not
doing any conversions in the first place.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
