Tom Lane a2794623d2 Extend the parser location infrastructure to include a location field in ... most node types used in expression trees (both before and after parse analysis). This allows us to place an error cursor in many situations where we formerly could not, because the information wasn't available beyond the very first level of parse analysis. There's a fair amount of work still to be done to persuade individual ereport() calls to actually include an error location, but this gets the initdb-forcing part of the work out of the way; and the situation is already markedly better than before for complaints about unimplementable implicit casts, such as CASE and UNION constructs with incompatible alternative data types. Per my proposal of a few days ago.		2008-08-28 23:09:48 +00:00
..
Makefile	Refactor backend makefiles to remove lots of duplicate code	2008-02-19 10:30:09 +00:00
prepjointree.c	Move exprType(), exprTypmod(), expression_tree_walker(), and related routines	2008-08-25 22:42:34 +00:00
prepqual.c	Extend the parser location infrastructure to include a location field in	2008-08-28 23:09:48 +00:00
preptlist.c	Extend the parser location infrastructure to include a location field in	2008-08-28 23:09:48 +00:00
prepunion.c	Extend the parser location infrastructure to include a location field in	2008-08-28 23:09:48 +00:00