postgresql/src/backend/parser
Tom Lane 0bb51aa967 Improve parsetree representation of special functions such as CURRENT_DATE.
We implement a dozen or so parameterless functions that the SQL standard
defines special syntax for.  Up to now, that was done by converting them
into more or less ad-hoc constructs such as "'now'::text::date".  That's
messy for multiple reasons: it exposes what should be implementation
details to users, and performance is worse than it needs to be in several
cases.  To improve matters, invent a new expression node type
SQLValueFunction that can represent any of these parameterless functions.

Bump catversion because this changes stored parsetrees for rules.

Discussion: <30058.1463091294@sss.pgh.pa.us>
2016-08-16 20:33:01 -04:00
..
.gitignore Convert cvsignore to gitignore, and add .gitignore for build targets. 2010-09-22 12:57:04 +02:00
analyze.c Make INSERT-from-multiple-VALUES-rows handle targetlist indirection better. 2016-08-03 16:37:03 -04:00
check_keywords.pl Update copyright for 2016 2016-01-02 13:33:40 -05:00
gram.y Improve parsetree representation of special functions such as CURRENT_DATE. 2016-08-16 20:33:01 -04:00
Makefile Move keywords.c/kwlookup.c into src/common/. 2016-03-23 20:22:08 -04:00
parse_agg.c Fix type-safety problem with parallel aggregate serial/deserialization. 2016-06-22 16:52:41 -04:00
parse_clause.c Run pgindent on a batch of (mostly-planner-related) source files. 2016-04-06 11:34:02 -04:00
parse_coerce.c Add defenses against putting expanded objects into Const nodes. 2016-01-21 12:56:08 -05:00
parse_collate.c Update copyright for 2016 2016-01-02 13:33:40 -05:00
parse_cte.c Update copyright for 2016 2016-01-02 13:33:40 -05:00
parse_expr.c Improve parsetree representation of special functions such as CURRENT_DATE. 2016-08-16 20:33:01 -04:00
parse_func.c Rethink node-level representation of partial-aggregation modes. 2016-06-26 14:33:38 -04:00
parse_node.c Update copyright for 2016 2016-01-02 13:33:40 -05:00
parse_oper.c Update copyright for 2016 2016-01-02 13:33:40 -05:00
parse_param.c Update copyright for 2016 2016-01-02 13:33:40 -05:00
parse_relation.c pgindent run for 9.6 2016-06-09 18:02:36 -04:00
parse_target.c Improve parsetree representation of special functions such as CURRENT_DATE. 2016-08-16 20:33:01 -04:00
parse_type.c Add defenses against putting expanded objects into Const nodes. 2016-01-21 12:56:08 -05:00
parse_utilcmd.c Improve documentation about CREATE TABLE ... LIKE. 2016-07-28 13:26:58 -04:00
parser.c Update copyright for 2016 2016-01-02 13:33:40 -05:00
README Move keywords.c/kwlookup.c into src/common/. 2016-03-23 20:22:08 -04:00
scan.l Update comment about allowing GUCs to change scanning. 2016-06-21 20:23:31 -04:00
scansup.c Introduce parse_ident() 2016-03-18 18:16:14 +03:00

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_func.c	handle functions, table.column and column identifiers
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.