Debian Codegraph @

src/backend/parser/README

raw
1 src/backend/parser/README
2
3 Parser
4 ======
5
6 This directory does more than tokenize and parse SQL queries. It also
7 creates Query structures for the various complex queries that are passed
8 to the optimizer and then executor.
9
10 parser.c things start here
11 scan.l break query into tokens
12 scansup.c handle escapes in input strings
13 gram.y parse the tokens and produce a "raw" parse tree
14 analyze.c top level of parse analysis for optimizable queries
15 parse_agg.c handle aggregates, like SUM(col1), AVG(col2), ...
16 parse_clause.c handle clauses like WHERE, ORDER BY, GROUP BY, ...
17 parse_coerce.c handle coercing expressions to different data types
18 parse_collate.c assign collation information in completed expressions
19 parse_cte.c handle Common Table Expressions (WITH clauses)
20 parse_expr.c handle expressions like col, col + 3, x = 3 or x = 4
21 parse_enr.c handle ephemeral named rels (trigger transition tables, ...)
22 parse_func.c handle functions, table.column and column identifiers
23 parse_jsontable.c handle JSON_TABLE
24 parse_merge.c handle MERGE
25 parse_node.c create nodes for various structures
26 parse_oper.c handle operators in expressions
27 parse_param.c handle Params (for the cases used in the core backend)
28 parse_relation.c support routines for tables and column handling
29 parse_target.c handle the result list of the query
30 parse_type.c support routines for data type handling
31 parse_utilcmd.c parse analysis for utility commands (done at execution time)
32
33 See also src/common/keywords.c, which contains the table of standard
34 keywords and the keyword lookup function. We separated that out because
35 various frontend code wants to use it too.