From 7e948d959477db19f0a8732f976a921636ee159f Mon Sep 17 00:00:00 2001 From: Amit Langote Date: Fri, 12 Apr 2024 17:23:08 +0900 Subject: [PATCH v3 2/3] JSON_TABLE: Use term path_expression more consistently SQL/JSON documentation uses path_expression for JSON path expressions but the bits added in bb766cde63b used json_path_specification. Replace with the former for consistency. Reported-by: Jian He Discussion: https://postgr.es/m/CACJufxG_e0QLCgaELrr2ZNz7AxPeGCNKAORe3fHtFCQLsH4J4Q@mail.gmail.com --- doc/src/sgml/func.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 8dfb42ad4d..545b1437df 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -18942,7 +18942,7 @@ where json_table_column is: { ERROR | NULL | EMPTY { ARRAY | OBJECT } | DEFAULT expression } ON ERROR | name type EXISTS PATH path_expression { ERROR | TRUE | FALSE | UNKNOWN } ON ERROR - | NESTED PATH json_path_specification AS json_path_name COLUMNS ( json_table_column , ... ) + | NESTED PATH path_expression AS json_path_name COLUMNS ( json_table_column , ... ) @@ -19083,7 +19083,7 @@ where json_table_column is: - NESTED PATH json_path_specification AS json_path_name + NESTED PATH path_expression AS json_path_name COLUMNS ( json_table_column , ... ) -- 2.43.0