| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: JSON and unicode surrogate pairs |
| Date: | 2013-06-12 01:17:30 |
| Message-ID: | 20130612011730.GB578390@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 11, 2013 at 08:42:26PM -0400, Andrew Dunstan wrote:
> If we work by analogy to Postgres' own handling of Unicode escapes,
> we'll raise an error on any Unicode escape beyond ASCII (not on input
> for legacy reasons, but on trying to process such datums). I gather that
> would meet your objection.
No objection here; that approach is free from the problem that caught my
attention in the other proposal.
--
Noah Misch
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2013-06-12 03:44:31 | Re: Adding IEEE 754:2008 decimal floating point and hardware support for it |
| Previous Message | Stephen Frost | 2013-06-12 01:15:20 | Re: Clean switchover |