postgresql/src/backend/parser
Tom Lane 6efbded6e4 Allow omitting one or both boundaries in an array slice specifier.
Omitted boundaries represent the upper or lower limit of the corresponding
array subscript.  This allows simpler specification of many common
use-cases.

(Revised version of commit 9246af6799)

YUriy Zhuravlev
2015-12-22 21:05:29 -05:00
..
.gitignore Convert cvsignore to gitignore, and add .gitignore for build targets. 2010-09-22 12:57:04 +02:00
Makefile Refactor flex and bison make rules 2012-10-11 06:57:04 -04:00
README Revise collation derivation method and expression-tree representation. 2011-03-19 20:30:08 -04:00
analyze.c Fix several bugs related to ON CONFLICT's EXCLUDED pseudo relation. 2015-10-03 15:12:10 +02:00
check_keywords.pl Update copyright for 2015 2015-01-06 11:43:47 -05:00
gram.y Allow omitting one or both boundaries in an array slice specifier. 2015-12-22 21:05:29 -05:00
keywords.c Update copyright for 2015 2015-01-06 11:43:47 -05:00
kwlookup.c Update copyright for 2015 2015-01-06 11:43:47 -05:00
parse_agg.c Message improvements 2015-11-16 21:39:23 -05:00
parse_clause.c Message improvements 2015-11-16 21:39:23 -05:00
parse_coerce.c Rename coerce_type() local variable. 2015-05-02 16:46:23 -04:00
parse_collate.c Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE. 2015-05-08 05:43:10 +02:00
parse_cte.c Update copyright for 2015 2015-01-06 11:43:47 -05:00
parse_expr.c Create new ParseExprKind for use by policy expressions. 2015-07-29 15:40:24 -07:00
parse_func.c Redesign tablesample method API, and do extensive code review. 2015-07-25 14:39:00 -04:00
parse_node.c Allow omitting one or both boundaries in an array slice specifier. 2015-12-22 21:05:29 -05:00
parse_oper.c Setup cursor position for schema-qualified elements 2015-03-18 14:48:02 -03:00
parse_param.c Update copyright for 2015 2015-01-06 11:43:47 -05:00
parse_relation.c Message improvements 2015-11-16 21:39:23 -05:00
parse_target.c Allow omitting one or both boundaries in an array slice specifier. 2015-12-22 21:05:29 -05:00
parse_type.c pgindent run for 9.5 2015-05-23 21:35:49 -04:00
parse_utilcmd.c Mark CHECK constraints declared NOT VALID valid if created with table. 2015-12-16 07:43:56 -05:00
parser.c Make operator precedence follow the SQL standard more closely. 2015-03-11 13:22:52 -04:00
scan.l Make operator precedence follow the SQL standard more closely. 2015-03-11 13:22:52 -04:00
scansup.c Update copyright for 2015 2015-01-06 11:43:47 -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
kwlookup.c	turn keywords into specific tokens
keywords.c	table of standard keywords (passed to kwlookup.c)
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)