| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com> |
| Cc: | Florian Pflug <fgp(at)phlo(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bernd Helmle <mailings(at)oopsware(dot)de>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, David Fetter <david(at)fetter(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Initial Review: JSON contrib modul was: Re: Another swing at JSON |
| Date: | 2011-07-20 04:32:11 |
| Message-ID: | CA+TgmoaF93djL07kQZO+hxHx+_q5A2PkUjo2_5e8wYoNKFKbXg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 19, 2011 at 9:03 PM, Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com> wrote:
> On Mon, Jul 18, 2011 at 7:36 PM, Florian Pflug <fgp(at)phlo(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joey Adams | 2011-07-20 04:40:29 | Re: Initial Review: JSON contrib modul was: Re: Another swing at JSON |
| Previous Message | Pavel Stehule | 2011-07-20 03:51:53 | Re: proposal: new contrib module plpgsql's embeded sql validator |