database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-08-08 06:02:22 +03:00
Code Activity

Fix unescaping of JSON Unicode escapes, especially for non-UTF8.

Browse Source 
Per discussion  on -hackers. We treat Unicode escapes when unescaping
them similarly to the way we treat them in PostgreSQL string literals.
Escapes in the ASCII range are always accepted, no matter what the
database encoding. Escapes for higher code points are only processed in
UTF8 databases, and attempts to process them in other databases will
result in an error. \u0000 is never unescaped, since it would result in
an impermissible null byte.
This commit is contained in:
Andrew Dunstan
2013-06-12 13:35:24 -04:00
parent c1d729b419
commit 78ed8e03c6
5 changed files with 1033 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/src/sgml/func.sgml
View File

@@ -10159,6 +10159,17 @@ table2-mapping
</para>
</note>
<note>
<para>
Many of these functions and operators will convert Unicode escapes
in the JSON text to the appropriate UTF8 character when the database encoding is UTF8. In
other encodings the escape sequence must be for an ASCII character, and any other code point
in a Unicode escape sequence will result in an error.
In general, it is best to avoid mixing Unicode escapes in JSON with a non-UTF8 database
encoding, if possible.
</para>
</note>
<note>
<para>
The <xref linkend="hstore"> extension has a cast from <type>hstore</type> to