You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
postgres/src/backend/parser
Tom Lane 72cfc17aef Improve handling of unknown-type literals in UNION/INTERSECT/EXCEPT. 15 years ago
..
.gitignore Convert cvsignore to gitignore, and add .gitignore for build targets. 15 years ago
Makefile Remove cvs keywords from all files. 15 years ago
README Remove cvs keywords from all files. 15 years ago
analyze.c Improve handling of unknown-type literals in UNION/INTERSECT/EXCEPT. 15 years ago
gram.y Remove 13 keywords that are used only for ROLE options. 15 years ago
keywords.c Stamp copyrights for year 2011. 15 years ago
kwlookup.c Stamp copyrights for year 2011. 15 years ago
parse_agg.c Per-column collation support 15 years ago
parse_clause.c Support data-modifying commands (INSERT/UPDATE/DELETE) in WITH. 15 years ago
parse_coerce.c Split CollateClause into separate raw and analyzed node types. 15 years ago
parse_cte.c Support data-modifying commands (INSERT/UPDATE/DELETE) in WITH. 15 years ago
parse_expr.c Split CollateClause into separate raw and analyzed node types. 15 years ago
parse_func.c Remove collation information from TypeName, where it does not belong. 15 years ago
parse_node.c Per-column collation support 15 years ago
parse_oper.c Per-column collation support 15 years ago
parse_param.c Per-column collation support 15 years ago
parse_relation.c Remove collation information from TypeName, where it does not belong. 15 years ago
parse_target.c Split CollateClause into separate raw and analyzed node types. 15 years ago
parse_type.c Split CollateClause into separate raw and analyzed node types. 15 years ago
parse_utilcmd.c Split CollateClause into separate raw and analyzed node types. 15 years ago
parser.c Stamp copyrights for year 2011. 15 years ago
scan.l Stamp copyrights for year 2011. 15 years ago
scansup.c Stamp copyrights for year 2011. 15 years ago

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_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)