postgresql/src/backend/parser
Michael Paquier 8961cb9a03 Fix typos in comments
The changes done in this commit impact comments with no direct
user-visible changes, with fixes for incorrect function, variable or
structure names.

Author: Alexander Lakhin
Discussion: https://postgr.es/m/e8c38840-596a-83d6-bd8d-cebc51111572@gmail.com
2023-05-02 12:23:08 +09:00
..
.gitignore Convert cvsignore to gitignore, and add .gitignore for build targets. 2010-09-22 12:57:04 +02:00
Makefile Revert SQL/JSON features 2022-09-01 17:07:14 -04:00
README Update src/backend/parser/README 2022-07-22 12:56:21 +02:00
analyze.c Invent GENERIC_PLAN option for EXPLAIN. 2023-03-24 17:07:22 -04:00
check_keywords.pl Update copyright for 2023 2023-01-02 15:00:37 -05:00
gram.y Fix typos in comments 2023-05-02 12:23:08 +09:00
gramparse.h Update copyright for 2023 2023-01-02 15:00:37 -05:00
meson.build Update copyright for 2023 2023-01-02 15:00:37 -05:00
parse_agg.c Fix failure to detect some cases of improperly-nested aggregates. 2023-03-13 12:40:28 -04:00
parse_clause.c Make Vars be outer-join-aware. 2023-01-30 13:16:20 -05:00
parse_coerce.c Make Vars be outer-join-aware. 2023-01-30 13:16:20 -05:00
parse_collate.c Update copyright for 2023 2023-01-02 15:00:37 -05:00
parse_cte.c Update copyright for 2023 2023-01-02 15:00:37 -05:00
parse_enr.c Update copyright for 2023 2023-01-02 15:00:37 -05:00
parse_expr.c Harmonize some more function parameter names. 2023-04-13 10:15:20 -07:00
parse_func.c Add SysCacheGetAttrNotNull for guaranteed not-null attrs 2023-03-25 22:49:33 +01:00
parse_merge.c Fix MERGE's test for unreachable WHEN clauses. 2023-01-10 14:17:47 +00:00
parse_node.c Allow underscores in integer and numeric constants. 2023-02-04 09:48:51 +00:00
parse_oper.c Remove useless casts to (void *) in hash_search() calls 2023-02-06 09:41:01 +01:00
parse_param.c Update copyright for 2023 2023-01-02 15:00:37 -05:00
parse_relation.c Fix more bugs caused by adding columns to the end of a view. 2023-03-07 18:21:53 -05:00
parse_target.c SQL/JSON: add standard JSON constructor functions 2023-03-29 12:11:36 +02:00
parse_type.c Update copyright for 2023 2023-01-02 15:00:37 -05:00
parse_utilcmd.c Fix crashes with CREATE SCHEMA AUTHORIZATION and schema elements 2023-04-28 19:29:12 +09:00
parser.c Code review for recent SQL/JSON commits 2023-04-04 14:04:30 +02:00
scan.l Allow underscores in integer and numeric constants. 2023-02-04 09:48:51 +00:00
scansup.c Update copyright for 2023 2023-01-02 15:00:37 -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_jsontable.c handle JSON_TABLE
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.