From b279e37015bba58f2e9752f177a6a4f4db2b1814 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Wed, 24 Apr 2024 11:31:47 +0200 Subject: [PATCH] doc: Correct jsonpath string literal escapes description The paragraph describing the JavaScript string literals allowed in jsonpath expressions unnecessarily mentions JSON by erroneously listing \v as allowed by JSON and mentioning the \xNN and \u{N...} backslash escapes as deviations from JSON when in fact both are accepted by ECMAScript/JavaScript. Fix this by only referring to JavaScript. Author: Erik Wienhold Discussion: https://www.postgresql.org/message-id/flat/1EB17DF9-2636-484B-9DD0-3CAB19C4F5C4@justatheory.com --- doc/src/sgml/json.sgml | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml index ec0e6bf742..54648c459c 100644 --- a/doc/src/sgml/json.sgml +++ b/doc/src/sgml/json.sgml @@ -803,21 +803,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 \", and to write a backslash itself, you must write \\. Other special backslash sequences - include those recognized in JSON strings: + include those recognized in JavaScript strings: \b, \f, \n, \r, \t, \v - for various ASCII control characters, and - \uNNNN 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, \xNN for a character code - written with only two hex digits, and - \u{N...} for a character - code written with 1 to 6 hex digits. + written with only two hex digits, + \uNNNN for a Unicode + character identified by its 4-hex-digit code point, and + \u{N...} for a Unicode + character code point written with 1 to 6 hex digits.