| From: | Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(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:40:29 |
| Message-ID: | CAARyMpDKzqj1dq3mfb3uBoMV4m3suNvxGrXYzEA+FmwoHwxM3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 20, 2011 at 12:32 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> 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.
We want to be able to handle \uXXXX escapes when the database encoding
is not UTF-8. We could leave them in place, but sooner or later
they'll need to be converted in order to unwrap or compare JSON
strings.
The approach being discussed is converting escapes to the database
encoding. This means escapes of characters not available in the
database encoding (e.g. \u266B in ISO-8859-1) will be forbidden.
The PostgreSQL parser (which also supports Unicode escapes) takes a
simpler approach: don't allow non-ASCII escapes unless the server
encoding is UTF-8.
- Joey
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yeb Havinga | 2011-07-20 07:02:59 | Re: [v9.2] Fix leaky-view problem, part 2 |
| Previous Message | Robert Haas | 2011-07-20 04:32:11 | Re: Initial Review: JSON contrib modul was: Re: Another swing at JSON |