1berry/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
postgres/src/include/parser/parse_relation.h

79 lines
2.8 KiB
C
Raw Normal View History

Change my-function-name-- to my_function_name, and optimizer renames.
1999-02-13 23:22:53 +00:00
/*-------------------------------------------------------------------------
Break parser functions into smaller files, group together.
1997-11-25 22:07:18 +00: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-19 00:26:20 +00:00
* parse_relation.h
* prototypes for parse_relation.c.
Break parser functions into smaller files, group together.
1997-11-25 22:07:18 +00:00
*
*
Tag appropriate files for rc3 Also performed an initial run through of upgrading our Copyright date to extend to 2005 ... first run here was very simple ... change everything where: grep 1996-2004 && the word 'Copyright' ... scanned through the generated list with 'less' first, and after, to make sure that I only picked up the right entries ...
2004-12-31 22:04:05 +00:00
* Portions Copyright (c) 1996-2005, 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 05:58:53 +00:00
* Portions Copyright (c) 1994, Regents of the University of California
Break parser functions into smaller files, group together.
1997-11-25 22:07:18 +00:00
*
Change expandRTE() and ResolveNew() back to taking just the single RTE of interest, rather than the whole rangetable list. This makes the API more understandable and avoids duplicate RTE lookups. This patch reverts no-longer-needed portions of my patch of 2004-08-19.
2005-06-04 19:19:42 +00:00
* $PostgreSQL: pgsql/src/include/parser/parse_relation.h,v 1.50 2005/06/04 19:19:42 tgl Exp $
Break parser functions into smaller files, group together.
1997-11-25 22:07:18 +00: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-19 00:26:20 +00:00
#ifndef PARSE_RELATION_H
#define PARSE_RELATION_H
Break parser functions into smaller files, group together.
1997-11-25 22:07:18 +00:00
Change #include's to use <> and "" as appropriate.
1999-07-15 23:04:24 +00:00
#include "parser/parse_node.h"
Break parser functions into smaller files, group together.
1997-11-25 22:07:18 +00:00
Add add_missing_from GUC variable. Nigel J. Andrews
2003-06-11 22:13:22 +00:00
extern bool add_missing_from;
Restructure representation of join alias variables. An explicit JOIN now has an RTE of its own, and references to its outputs now are Vars referencing the JOIN RTE, rather than CASE-expressions. This allows reverse-listing in ruleutils.c to use the correct alias easily, rather than painfully reverse-engineering the alias namespace as it used to do. Also, nested FULL JOINs work correctly, because the result of the inner joins are simple Vars that the planner can cope with. This fixes a bug reported a couple times now, notably by Tatsuo on 18-Nov-01. The alias Vars are expanded into COALESCE expressions where needed at the very end of planning, rather than during parsing. Also, beginnings of support for showing plan qualifier expressions in EXPLAIN. There are probably still cases that need work. initdb forced due to change of stored-rule representation.
2002-03-12 00:52:10 +00:00
extern RangeTblEntry *refnameRangeTblEntry(ParseState *pstate,
pgindent run.
2002-09-04 20:31:48 +00:00
const char *schemaname,
const char *refname,
int *sublevels_up);
Change scoping of table and join refnames to conform to SQL92: a JOIN clause with an alias is a <subquery> and therefore hides table references appearing within it, according to the spec. This is the same as the preliminary patch I posted to pgsql-patches yesterday, plus some really grotty code in ruleutils.c to reverse-list a query tree with the correct alias name depending on context. I'd rather not have done that, but unless we want to force another initdb for 7.1, there's no other way for now.
2001-02-14 21:35:07 +00:00
extern void checkNameSpaceConflicts(ParseState *pstate, Node *namespace1,
pgindent run. Make it all clean.
2001-03-22 04:01:46 +00:00
Node *namespace2);
First cut at full support for OUTER JOINs. There are still a few loose ends to clean up (see my message of same date to pghackers), but mostly it works. INITDB REQUIRED!
2000-09-12 21:07:18 +00:00
extern int RTERangeTablePosn(ParseState *pstate,
pgindent run. Make it all clean.
2001-03-22 04:01:46 +00:00
RangeTblEntry *rte,
int *sublevels_up);
Get rid of crocky use of RangeVar nodes in parser to represent partially transformed whole-row variables. Cleaner to use regular whole-row Vars.
2004-04-02 19:07:02 +00:00
extern RangeTblEntry *GetRTEByRangeTablePosn(ParseState *pstate,
Pgindent run for 8.0.
2004-08-29 05:07:03 +00:00
int varno,
int sublevels_up);
Get rid of crocky use of RangeVar nodes in parser to represent partially transformed whole-row variables. Cleaner to use regular whole-row Vars.
2004-04-02 19:07:02 +00:00
extern Node *scanRTEForColumn(ParseState *pstate, RangeTblEntry *rte,
Pgindent run for 8.0.
2004-08-29 05:07:03 +00:00
char *colname);
Tweak findTargetlistEntry so that bare names occurring in GROUP BY clauses are sought first as local FROM columns, then as local SELECT-list aliases, and finally as outer FROM columns; the former behavior made outer FROM columns take precedence over aliases. This does not change spec conformance because SQL99 allows only the first case anyway, and it seems more useful and self-consistent. Per gripe from Dennis Bjorklund 2004-04-05.
2004-04-18 18:12:58 +00:00
extern Node *colNameToVar(ParseState *pstate, char *colname, bool localonly);
Cause schema-qualified FROM items and schema-qualified variable references to behave according to SQL92 (or according to my current understanding of same, anyway). Per pghackers discussion way back in March 2002: thread 'Do FROM items of different schemas conflict?'
2002-08-08 01:44:31 +00:00
extern Node *qualifiedNameToVar(ParseState *pstate,
pgindent run.
2002-09-04 20:31:48 +00:00
char *schemaname,
char *refname,
char *colname,
bool implicitRTEOK);
OK, folks, here is the pgindent output.
1998-09-01 04:40:42 +00:00
extern RangeTblEntry *addRangeTableEntry(ParseState *pstate,
A little further progress on schemas: push down RangeVars into addRangeTableEntry calls. Remove relname field from RTEs, since it will no longer be a useful unique identifier of relations; we want to encourage people to rely on the relation OID instead. Further work on dumping qual expressions in EXPLAIN, too.
2002-03-22 02:56:37 +00:00
RangeVar *relation,
Alias *alias,
bool inh,
bool inFromCl);
extern RangeTblEntry *addRangeTableEntryForRelation(ParseState *pstate,
Change addRangeTableEntryForRelation() to take a Relation pointer instead of just a relation OID, thereby not having to open the relation for itself. This actually saves code rather than adding it for most of the existing callers, which had the rel open already. The main point though is to be able to use this rather than plain addRangeTableEntry in setTargetTable, thus saving one relation_openrv/relation_close cycle for every INSERT, UPDATE, or DELETE. Seems to provide a several percent win on simple INSERTs.
2005-04-13 16:50:55 +00:00
Relation rel,
pgindent run.
2002-09-04 20:31:48 +00:00
Alias *alias,
bool inh,
bool inFromCl);
Subselects in FROM clause, per ISO syntax: FROM (SELECT ...) [AS] alias. (Don't forget that an alias is required.) Views reimplemented as expanding to subselect-in-FROM. Grouping, aggregates, DISTINCT in views actually work now (he says optimistically). No UNION support in subselects/views yet, but I have some ideas about that. Rule-related permissions checking moved out of rewriter and into executor. INITDB REQUIRED!
2000-09-29 18:21:41 +00:00
extern RangeTblEntry *addRangeTableEntryForSubquery(ParseState *pstate,
pgindent run. Make it all clean.
2001-03-22 04:01:46 +00:00
Query *subquery,
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 16:02:16 +00:00
Alias *alias,
pgindent run. Make it all clean.
2001-03-22 04:01:46 +00:00
bool inFromCl);
First pass at set-returning-functions in FROM, by Joe Conway with some kibitzing from Tom Lane. Not everything works yet, and there's no documentation or regression test, but let's commit this so Joe doesn't need to cope with tracking changes in so many files ...
2002-05-12 20:10:05 +00:00
extern RangeTblEntry *addRangeTableEntryForFunction(ParseState *pstate,
pgindent run.
2002-09-04 20:31:48 +00:00
char *funcname,
Node *funcexpr,
RangeFunction *rangefunc,
bool inFromCl);
Restructure representation of join alias variables. An explicit JOIN now has an RTE of its own, and references to its outputs now are Vars referencing the JOIN RTE, rather than CASE-expressions. This allows reverse-listing in ruleutils.c to use the correct alias easily, rather than painfully reverse-engineering the alias namespace as it used to do. Also, nested FULL JOINs work correctly, because the result of the inner joins are simple Vars that the planner can cope with. This fixes a bug reported a couple times now, notably by Tatsuo on 18-Nov-01. The alias Vars are expanded into COALESCE expressions where needed at the very end of planning, rather than during parsing. Also, beginnings of support for showing plan qualifier expressions in EXPLAIN. There are probably still cases that need work. initdb forced due to change of stored-rule representation.
2002-03-12 00:52:10 +00:00
extern RangeTblEntry *addRangeTableEntryForJoin(ParseState *pstate,
List *colnames,
JoinType jointype,
Second try at fixing join alias variables. Instead of attaching miscellaneous lists to join RTEs, attach a list of Vars and COALESCE expressions that will replace the join's alias variables during planning. This simplifies flatten_join_alias_vars while still making it easy to fix up varno references when transforming the query tree. Add regression test cases for interactions of subqueries with outer joins.
2002-04-28 19:54:29 +00:00
List *aliasvars,
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 16:02:16 +00:00
Alias *alias,
Restructure representation of join alias variables. An explicit JOIN now has an RTE of its own, and references to its outputs now are Vars referencing the JOIN RTE, rather than CASE-expressions. This allows reverse-listing in ruleutils.c to use the correct alias easily, rather than painfully reverse-engineering the alias namespace as it used to do. Also, nested FULL JOINs work correctly, because the result of the inner joins are simple Vars that the planner can cope with. This fixes a bug reported a couple times now, notably by Tatsuo on 18-Nov-01. The alias Vars are expanded into COALESCE expressions where needed at the very end of planning, rather than during parsing. Also, beginnings of support for showing plan qualifier expressions in EXPLAIN. There are probably still cases that need work. initdb forced due to change of stored-rule representation.
2002-03-12 00:52:10 +00:00
bool inFromCl);
Change scoping of table and join refnames to conform to SQL92: a JOIN clause with an alias is a <subquery> and therefore hides table references appearing within it, according to the spec. This is the same as the preliminary patch I posted to pgsql-patches yesterday, plus some really grotty code in ruleutils.c to reverse-list a query tree with the correct alias name depending on context. I'd rather not have done that, but unless we want to force another initdb for 7.1, there's no other way for now.
2001-02-14 21:35:07 +00:00
extern void addRTEtoQuery(ParseState *pstate, RangeTblEntry *rte,
pgindent run. Make it all clean.
2001-03-22 04:01:46 +00:00
bool addToJoinList, bool addToNameSpace);
A little further progress on schemas: push down RangeVars into addRangeTableEntry calls. Remove relname field from RTEs, since it will no longer be a useful unique identifier of relations; we want to encourage people to rely on the relation OID instead. Further work on dumping qual expressions in EXPLAIN, too.
2002-03-22 02:56:37 +00:00
extern RangeTblEntry *addImplicitRTE(ParseState *pstate, RangeVar *relation);
Change expandRTE() and ResolveNew() back to taking just the single RTE of interest, rather than the whole rangetable list. This makes the API more understandable and avoids duplicate RTE lookups. This patch reverts no-longer-needed portions of my patch of 2004-08-19.
2005-06-04 19:19:42 +00:00
extern void expandRTE(RangeTblEntry *rte, int rtindex, int sublevels_up,
Pgindent run for 8.0.
2004-08-29 05:07:03 +00:00
bool include_dropped,
List **colnames, List **colvars);
Change expandRTE() and ResolveNew() back to taking just the single RTE of interest, rather than the whole rangetable list. This makes the API more understandable and avoids duplicate RTE lookups. This patch reverts no-longer-needed portions of my patch of 2004-08-19.
2005-06-04 19:19:42 +00:00
extern List *expandRelAttrs(ParseState *pstate, RangeTblEntry *rte,
Pgindent run for 8.0.
2004-08-29 05:07:03 +00:00
int rtindex, int sublevels_up);
ALTER TABLE DROP COLUMN works. Patch by Christopher Kings-Lynne, code review by Tom Lane. Remaining issues: functions that take or return tuple types are likely to break if one drops (or adds!) a column in the table defining the type. Need to think about what to do here. Along the way: some code review for recent COPY changes; mark system columns attnotnull = true where appropriate, per discussion a month ago.
2002-08-02 18:15:10 +00:00
extern int attnameAttNum(Relation rd, const char *attname, bool sysColOK);
Fix foreign keys on system columns.
2001-10-23 17:39:03 +00:00
extern Name attnumAttName(Relation rd, int attid);
pgindent run before 6.3 release, with Thomas' requested changes.
1998-02-26 04:46:47 +00:00
extern Oid attnumTypeId(Relation rd, int attid);
Another pgindent run. Fixes enum indenting, and improves #endif spacing. Also adds space for one-line comments.
2001-10-28 06:26:15 +00:00
New pgindent run with fixes suggested by Tom. Patch manually reviewed, initdb/regression tests pass.
2001-11-05 17:46:40 +00:00
#endif /* PARSE_RELATION_H */
Reference in New Issue Copy Permalink