Re: jsonb, unicode escapes and escaped backslashes
| От | Tom Lane |
|---|---|
| Тема | Re: jsonb, unicode escapes and escaped backslashes |
| Дата | |
| Msg-id | 32226.1422571163@sss.pgh.pa.us обсуждение |
| Ответ на | Re: jsonb, unicode escapes and escaped backslashes (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: jsonb, unicode escapes and escaped backslashes
Re: jsonb, unicode escapes and escaped backslashes |
| Список | 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 по дате отправления: