postgresql/src/backend/parser
Amit Langote 6185c9737c Add SQL/JSON query functions
This introduces the following SQL/JSON functions for querying JSON
data using jsonpath expressions:

JSON_EXISTS(), which can be used to apply a jsonpath expression to a
JSON value to check if it yields any values.

JSON_QUERY(), which can be used to to apply a jsonpath expression to
a JSON value to get a JSON object, an array, or a string.  There are
various options to control whether multi-value result uses array
wrappers and whether the singleton scalar strings are quoted or not.

JSON_VALUE(), which can be used to apply a jsonpath expression to a
JSON value to return a single scalar value, producing an error if it
multiple values are matched.

Both JSON_VALUE() and JSON_QUERY() functions have options for
handling EMPTY and ERROR conditions, which can be used to specify
the behavior when no values are matched and when an error occurs
during jsonpath evaluation, respectively.

Author: Nikita Glukhov <n.gluhov@postgrespro.ru>
Author: Teodor Sigaev <teodor@sigaev.ru>
Author: Oleg Bartunov <obartunov@gmail.com>
Author: Alexander Korotkov <aekorotkov@gmail.com>
Author: Andrew Dunstan <andrew@dunslane.net>
Author: Amit Langote <amitlangote09@gmail.com>
Author: Peter Eisentraut <peter@eisentraut.org>
Author: Jian He <jian.universality@gmail.com>

Reviewers have included (in no particular order):

Andres Freund, Alexander Korotkov, Pavel Stehule, Andrew Alsup,
Erik Rijkers, Zihong Yu, Himanshu Upadhyaya, Daniel Gustafsson,
Justin Pryzby, Álvaro Herrera, Jian He, Anton A. Melnikov,
Nikita Malakhov, Peter Eisentraut, Tomas Vondra

Discussion: https://postgr.es/m/cd0bb935-0158-78a7-08b5-904886deac4b@postgrespro.ru
Discussion: https://postgr.es/m/20220616233130.rparivafipt6doj3@alap3.anarazel.de
Discussion: https://postgr.es/m/abd9b83b-aa66-f230-3d6d-734817f0995d%40postgresql.org
Discussion: https://postgr.es/m/CA+HiwqHROpf9e644D8BRqYvaAPmgBZVup-xKMDPk-nd4EpgzHw@mail.gmail.com
Discussion: https://postgr.es/m/CA+HiwqE4XTdfb1nW=Ojoy_tQSRhYt-q_kb6i5d4xcKyrLC1Nbg@mail.gmail.com
2024-03-21 17:07:03 +09:00
..
.gitignore Convert cvsignore to gitignore, and add .gitignore for build targets. 2010-09-22 12:57:04 +02:00
Makefile Remove distprep 2023-11-06 15:18:04 +01:00
README Remove outdated reference to a removed file 2023-06-15 22:35:42 +09:00
analyze.c Add RETURNING support to MERGE. 2024-03-17 13:58:59 +00:00
check_keywords.pl Update copyright for 2024 2024-01-03 20:49:05 -05:00
gram.y Add SQL/JSON query functions 2024-03-21 17:07:03 +09:00
gramparse.h Update copyright for 2024 2024-01-03 20:49:05 -05:00
meson.build Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_agg.c Add RETURNING support to MERGE. 2024-03-17 13:58:59 +00:00
parse_clause.c Remove unused #include's from backend .c files 2024-03-04 12:02:20 +01:00
parse_coerce.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_collate.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_cte.c Add RETURNING support to MERGE. 2024-03-17 13:58:59 +00:00
parse_enr.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_expr.c Add SQL/JSON query functions 2024-03-21 17:07:03 +09:00
parse_func.c Add RETURNING support to MERGE. 2024-03-17 13:58:59 +00:00
parse_merge.c Add RETURNING support to MERGE. 2024-03-17 13:58:59 +00:00
parse_node.c Remove unused #include's from backend .c files 2024-03-04 12:02:20 +01:00
parse_oper.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_param.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_relation.c Add RETURNING support to MERGE. 2024-03-17 13:58:59 +00:00
parse_target.c Add SQL/JSON query functions 2024-03-21 17:07:03 +09:00
parse_type.c Add a const decoration 2024-01-25 13:34:49 +01:00
parse_utilcmd.c Revert "Improve compression and storage support with inheritance" 2024-02-20 11:10:59 +01:00
parser.c Make the order of the header file includes consistent 2024-03-13 15:07:00 +01:00
scan.l Update copyright for 2024 2024-01-03 20:49:05 -05:00
scansup.c Update copyright for 2024 2024-01-03 20:49:05 -05:00

README

src/backend/parser/README

Parser
======

This directory does more than tokenize and parse SQL queries.  It also
creates Query structures for the various complex queries that are passed
to the optimizer and then executor.

parser.c	things start here
scan.l		break query into tokens
scansup.c	handle escapes in input strings
gram.y		parse the tokens and produce a "raw" parse tree
analyze.c	top level of parse analysis for optimizable queries
parse_agg.c	handle aggregates, like SUM(col1),  AVG(col2), ...
parse_clause.c	handle clauses like WHERE, ORDER BY, GROUP BY, ...
parse_coerce.c	handle coercing expressions to different data types
parse_collate.c	assign collation information in completed expressions
parse_cte.c	handle Common Table Expressions (WITH clauses)
parse_expr.c	handle expressions like col, col + 3, x = 3 or x = 4
parse_enr.c	handle ephemeral named rels (trigger transition tables, ...)
parse_func.c	handle functions, table.column and column identifiers
parse_merge.c	handle MERGE
parse_node.c	create nodes for various structures
parse_oper.c	handle operators in expressions
parse_param.c	handle Params (for the cases used in the core backend)
parse_relation.c support routines for tables and column handling
parse_target.c	handle the result list of the query
parse_type.c	support routines for data type handling
parse_utilcmd.c	parse analysis for utility commands (done at execution time)

See also src/common/keywords.c, which contains the table of standard
keywords and the keyword lookup function.  We separated that out because
various frontend code wants to use it too.