Re: jsonb, unicode escapes and escaped backslashes - Mailing list pgsql-hackers

From Tom Lane
Subject Re: jsonb, unicode escapes and escaped backslashes
Date
Msg-id 32226.1422571163@sss.pgh.pa.us
Whole thread Raw
In response to Re: jsonb, unicode escapes and escaped backslashes  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: jsonb, unicode escapes and escaped backslashes
Re: jsonb, unicode escapes and escaped backslashes
List pgsql-hackers
Robert Haas <robertmhaas@gmail.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



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: jsonb, unicode escapes and escaped backslashes
Next
From: Andrew Dunstan
Date:
Subject: Re: jsonb, unicode escapes and escaped backslashes