diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-05-21 05:05:26 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-05-21 05:05:26 +0000 |
commit | e75d99818dd3940be997520e64db8c9e3b207e39 (patch) | |
tree | 0003ca0de74fcc8d18433e34ea68d2e7aaf06b7c /doc/src/sgml/json.sgml | |
parent | Releasing progress-linux version 15.6-0+deb12u1~progress6.99u1. (diff) | |
download | postgresql-15-e75d99818dd3940be997520e64db8c9e3b207e39.tar.xz postgresql-15-e75d99818dd3940be997520e64db8c9e3b207e39.zip |
Merging upstream version 15.7.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'doc/src/sgml/json.sgml')
-rw-r--r-- | doc/src/sgml/json.sgml | 17 |
1 files changed, 8 insertions, 9 deletions
diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml index 4182d69..06e2d65 100644 --- a/doc/src/sgml/json.sgml +++ b/doc/src/sgml/json.sgml @@ -13,7 +13,7 @@ <para> JSON data types are for storing JSON (JavaScript Object Notation) - data, as specified in <ulink url="https://tools.ietf.org/html/rfc7159">RFC + data, as specified in <ulink url="https://datatracker.ietf.org/doc/html/rfc7159">RFC 7159</ulink>. Such data can also be stored as <type>text</type>, but the JSON data types have the advantage of enforcing that each stored value is valid according to the JSON rules. There are also @@ -791,21 +791,20 @@ UPDATE table_name SET jsonb_field[1]['a'] = '1'; In particular, the way to write a double quote within an embedded string literal is <literal>\"</literal>, and to write a backslash itself, you must write <literal>\\</literal>. Other special backslash sequences - include those recognized in JSON strings: + include those recognized in JavaScript strings: <literal>\b</literal>, <literal>\f</literal>, <literal>\n</literal>, <literal>\r</literal>, <literal>\t</literal>, <literal>\v</literal> - for various ASCII control characters, and - <literal>\u<replaceable>NNNN</replaceable></literal> for a Unicode - character identified by its 4-hex-digit code point. The backslash - syntax also includes two cases not allowed by JSON: + for various ASCII control characters, <literal>\x<replaceable>NN</replaceable></literal> for a character code - written with only two hex digits, and - <literal>\u{<replaceable>N...</replaceable>}</literal> for a character - code written with 1 to 6 hex digits. + written with only two hex digits, + <literal>\u<replaceable>NNNN</replaceable></literal> for a Unicode + character identified by its 4-hex-digit code point, and + <literal>\u{<replaceable>N...</replaceable>}</literal> for a Unicode + character code point written with 1 to 6 hex digits. </para> <para> |