postgresql/src/include/parser/parse_expr.h

/*-------------------------------------------------------------------------
 *
 * parse_expr.h
 *	  handle expressions in parser
 *
 * Portions Copyright (c) 1996-2021, PostgreSQL Global Development Group
 * Portions Copyright (c) 1994, Regents of the University of California
 *
 * src/include/parser/parse_expr.h
 *
 *-------------------------------------------------------------------------
 */
#ifndef PARSE_EXPR_H
#define PARSE_EXPR_H

#include "parser/parse_node.h"

/* GUC parameters */
extern bool Transform_null_equals;

extern Node *transformExpr(ParseState *pstate, Node *expr, ParseExprKind exprKind);

extern const char *ParseExprKindName(ParseExprKind exprKind);

#endif							/* PARSE_EXPR_H */
Break parser functions into smaller files, group together. 1997-11-25 17:07:18 -05:00			`/*-------------------------------------------------------------------------`
			`*`
Rewrite parser's handling of INSERT ... SELECT so that processing of the SELECT part of the statement is just like a plain SELECT. All INSERT-specific processing happens after the SELECT parsing is done. This eliminates many problems, e.g. INSERT ... SELECT ... GROUP BY using the wrong column labels. Ensure that DEFAULT clauses are coerced to the target column type, whether or not stored clause produces the right type. Substantial cleanup of parser's array support. 1999-07-18 20:26:20 -04:00			`* parse_expr.h`
Move exprType(), exprTypmod(), expression_tree_walker(), and related routines into nodes/nodeFuncs, so as to reduce wanton cross-subsystem #includes inside the backend. There's probably more that should be done along this line, but this is a start anyway. 2008-08-25 18:42:34 -04:00			`* handle expressions in parser`
Break parser functions into smaller files, group together. 1997-11-25 17:07:18 -05:00			`*`
Update copyright for 2021 Backpatch-through: 9.5 2021-01-02 13:06:25 -05:00			`* Portions Copyright (c) 1996-2021, PostgreSQL Global Development Group`
Add: * Portions Copyright (c) 1996-2000, PostgreSQL, Inc to all files copyright Regents of Berkeley. Man, that's a lot of files. 2000-01-26 00:58:53 -05:00			`* Portions Copyright (c) 1994, Regents of the University of California`
Break parser functions into smaller files, group together. 1997-11-25 17:07:18 -05:00			`*`
Remove cvs keywords from all files. 2010-09-20 16:08:53 -04:00			`* src/include/parser/parse_expr.h`
Break parser functions into smaller files, group together. 1997-11-25 17:07:18 -05:00			`*`
			`*-------------------------------------------------------------------------`
			`*/`
			`#ifndef PARSE_EXPR_H`
			`#define PARSE_EXPR_H`

Change #include's to use <> and "" as appropriate. 1999-07-15 19:04:24 -04:00			`#include "parser/parse_node.h"`
Break parser functions into smaller files, group together. 1997-11-25 17:07:18 -05:00
First phase of SCHEMA changes, concentrating on fixing the grammar and the parsetree representation. As yet we don't do anything with schema names, just drop 'em on the floor; but you can enter schema-compatible command syntax, and there's even a primitive CREATE SCHEMA command. No doc updates yet, except to note that you can now extract a field from a function-returning-row's result with (foo(...)).fieldname. 2002-03-21 11:02:16 -05:00			`/* GUC parameters */`
Provide tunable knob for x = NULL -> x IS NULL transformation, default to off. 2001-09-20 10:20:28 -04:00			`extern bool Transform_null_equals;`
Add safety check on expression nesting depth. Default value is set by a config.h #define, and the runtime value can be controlled via SET. 2000-03-17 00:29:07 -05:00
Centralize the logic for detecting misplaced aggregates, window funcs, etc. Formerly we relied on checking after-the-fact to see if an expression contained aggregates, window functions, or sub-selects when it shouldn't. This is grotty, easily forgotten (indeed, we had forgotten to teach DefineIndex about rejecting window functions), and none too efficient since it requires extra traversals of the parse tree. To improve matters, define an enum type that classifies all SQL sub-expressions, store it in ParseState to show what kind of expression we are currently parsing, and make transformAggregateCall, transformWindowFuncCall, and transformSubLink check the expression type and throw error if the type indicates the construct is disallowed. This allows removal of a large number of ad-hoc checks scattered around the code base. The enum type is sufficiently fine-grained that we can still produce error messages of at least the same specificity as before. Bringing these error checks together revealed that we'd been none too consistent about phrasing of the error messages, so standardize the wording a bit. Also, rewrite checking of aggregate arguments so that it requires only one traversal of the arguments, rather than up to three as before. In passing, clean up some more comments left over from add_missing_from support, and annotate some tests that I think are dead code now that that's gone. (I didn't risk actually removing said dead code, though.) 2012-08-10 11:35:33 -04:00			`extern Node transformExpr(ParseState pstate, Node *expr, ParseExprKind exprKind);`

			`extern const char *ParseExprKindName(ParseExprKind exprKind);`
Another pgindent run. Fixes enum indenting, and improves #endif spacing. Also adds space for one-line comments. 2001-10-28 01:26:15 -05:00
Phase 2 of pgindent updates. Change pg_bsd_indent to follow upstream rules for placement of comments to the right of code, and remove pgindent hack that caused comments following #endif to not obey the general rule. Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using the published version of pg_bsd_indent, but a hacked-up version that tried to minimize the amount of movement of comments to the right of code. The situation of interest is where such a comment has to be moved to the right of its default placement at column 33 because there's code there. BSD indent has always moved right in units of tab stops in such cases --- but in the previous incarnation, indent was working in 8-space tab stops, while now it knows we use 4-space tabs. So the net result is that in about half the cases, such comments are placed one tab stop left of before. This is better all around: it leaves more room on the line for comment text, and it means that in such cases the comment uniformly starts at the next 4-space tab stop after the code, rather than sometimes one and sometimes two tabs after. Also, ensure that comments following #endif are indented the same as comments following other preprocessor commands such as #else. That inconsistency turns out to have been self-inflicted damage from a poorly-thought-through post-indent "fixup" in pgindent. This patch is much less interesting than the first round of indent changes, but also bulkier, so I thought it best to separate the effects. Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us 2017-06-21 15:18:54 -04:00			`#endif /* PARSE_EXPR_H */`