Re: jsonb, unicode escapes and escaped backslashes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: jsonb, unicode escapes and escaped backslashes
Date: 2015-01-29 22:39:23
Message-ID: 32226.1422571163@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I have yet to understand what we fix by banning \u0000. How is 0000
> different from any other four-digit hexadecimal number that's not a
> valid character in the current encoding? What does banning that one
> particular value do?

BTW, as to the point about encoding violations: we *already* ban \uXXXX
sequences that don't correspond to valid characters in the current
encoding. The attempt to exclude U+0000 from the set of banned characters
was ill-advised, plain and simple.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2015-01-29 23:02:02 Re: jsonb, unicode escapes and escaped backslashes
Previous Message Andrew Dunstan 2015-01-29 22:30:54 Re: jsonb, unicode escapes and escaped backslashes