postgresql/src/backend/parser
Peter Eisentraut a2da77cdb4 Change return type of EXTRACT to numeric
The previous implementation of EXTRACT mapped internally to
date_part(), which returned type double precision (since it was
implemented long before the numeric type existed).  This can lead to
imprecise output in some cases, so returning numeric would be
preferrable.  Changing the return type of an existing function is a
bit risky, so instead we do the following:  We implement a new set of
functions, which are now called "extract", in parallel to the existing
date_part functions.  They work the same way internally but use
numeric instead of float8.  The EXTRACT construct is now mapped by the
parser to these new extract functions.  That way, dumps of views
etc. from old versions (which would use date_part) continue to work
unchanged, but new uses will map to the new extract functions.

Additionally, the reverse compilation of EXTRACT now reproduces the
original syntax, using the new mechanism introduced in
40c24bfef9.

The following minor changes of behavior result from the new
implementation:

- The column name from an isolated EXTRACT call is now "extract"
  instead of "date_part".

- Extract from date now rejects inappropriate field names such as
  HOUR.  It was previously mapped internally to extract from
  timestamp, so it would silently accept everything appropriate for
  timestamp.

- Return values when extracting fields with possibly fractional
  values, such as second and epoch, now have the full scale that the
  value has internally (so, for example, '1.000000' instead of just
  '1').

Reported-by: Petr Fedorov <petr.fedorov@phystech.edu>
Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: https://www.postgresql.org/message-id/flat/42b73d2d-da12-ba9f-570a-420e0cce19d9@phystech.edu
2021-04-06 07:20:42 +02:00
..
.gitignore Convert cvsignore to gitignore, and add .gitignore for build targets. 2010-09-22 12:57:04 +02:00
analyze.c Allow an alias to be attached to a JOIN ... USING 2021-03-31 17:10:50 +02:00
check_keywords.pl Update copyright for 2021 2021-01-02 13:06:25 -05:00
gram.y Change return type of EXTRACT to numeric 2021-04-06 07:20:42 +02:00
Makefile Split all OBJS style lines in makefiles into one-line-per-entry style. 2019-11-05 14:41:07 -08:00
parse_agg.c Extended statistics on expressions 2021-03-27 00:01:11 +01:00
parse_clause.c Allow an alias to be attached to a JOIN ... USING 2021-03-31 17:10:50 +02:00
parse_coerce.c Re-implement pl/pgsql's expression and assignment parsing. 2021-01-04 11:52:00 -05:00
parse_collate.c Update copyright for 2021 2021-01-02 13:06:25 -05:00
parse_cte.c Fix list-manipulation bug in WITH RECURSIVE processing. 2021-02-25 20:47:32 -05:00
parse_enr.c Update copyright for 2021 2021-01-02 13:06:25 -05:00
parse_expr.c Allow an alias to be attached to a JOIN ... USING 2021-03-31 17:10:50 +02:00
parse_func.c Add errhint_plural() function and make use of it 2021-03-31 09:16:25 +02:00
parse_node.c Update copyright for 2021 2021-01-02 13:06:25 -05:00
parse_oper.c Update copyright for 2021 2021-01-02 13:06:25 -05:00
parse_param.c Update copyright for 2021 2021-01-02 13:06:25 -05:00
parse_relation.c Allow an alias to be attached to a JOIN ... USING 2021-03-31 17:10:50 +02:00
parse_target.c Remove no-longer-used RTE argument of markVarForSelectPriv(). 2021-02-11 11:23:25 -05:00
parse_type.c Add the ability for the core grammar to have more than one parse target. 2021-01-04 11:03:22 -05:00
parse_utilcmd.c Extended statistics on expressions 2021-03-27 00:01:11 +01:00
parser.c Re-implement pl/pgsql's expression and assignment parsing. 2021-01-04 11:52:00 -05:00
README Move keywords.c/kwlookup.c into src/common/. 2016-03-23 20:22:08 -04:00
scan.l Update copyright for 2021 2021-01-02 13:06:25 -05:00
scansup.c Update copyright for 2021 2021-01-02 13:06:25 -05: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.