From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: doc: Correct jsonpath string literal escapes description |
Date: | 2024-04-24 09:39:16 |
Message-ID: | E1rzZ5v-003deZ-PV@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
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 <ewie(at)ewie(dot)name>
Discussion: https://www.postgresql.org/message-id/flat/1EB17DF9-2636-484B-9DD0-3CAB19C4F5C4(at)justatheory(dot)com
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/a7ed15f3ab8160d627e8281bd62a048a4fca371f
Modified Files
--------------
doc/src/sgml/json.sgml | 15 +++++++--------
1 file changed, 7 insertions(+), 8 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2024-04-24 10:14:15 | pgsql: pg_combinebackup: Add --version to --help output |
Previous Message | Peter Eisentraut | 2024-04-24 09:19:12 | pgsql: pg_combinebackup: Put newer options in consistent order in --hel |