mirror of
https://github.com/postgres/postgres.git
synced 2026-02-11 14:53:31 -05:00
b310b6e31c
All expression nodes now have an explicit output-collation field, unless they are known to only return a noncollatable data type (such as boolean or record). Also, nodes that can invoke collation-aware functions store a separate field that is the collation value to pass to the function. This avoids confusion that arises when a function has collatable inputs and noncollatable output type, or vice versa. Also, replace the parser's on-the-fly collation assignment method with a post-pass over the completed expression tree. This allows us to use a more complex (and hopefully more nearly spec-compliant) assignment rule without paying for it in extra storage in every expression node. Fix assorted bugs in the planner's handling of collations by making collation one of the defining properties of an EquivalenceClass and by converting CollateExprs into discardable RelabelType nodes during expression preprocessing.
64 lines
1.6 KiB
Makefile
64 lines
1.6 KiB
Makefile
#-------------------------------------------------------------------------
|
|
#
|
|
# Makefile for parser
|
|
#
|
|
# src/backend/parser/Makefile
|
|
#
|
|
#-------------------------------------------------------------------------
|
|
|
|
subdir = src/backend/parser
|
|
top_builddir = ../../..
|
|
include $(top_builddir)/src/Makefile.global
|
|
|
|
override CPPFLAGS := -I. -I$(srcdir) $(CPPFLAGS)
|
|
|
|
OBJS= analyze.o gram.o keywords.o kwlookup.o parser.o \
|
|
parse_agg.o parse_clause.o parse_coerce.o parse_collate.o parse_cte.o \
|
|
parse_expr.o parse_func.o parse_node.o parse_oper.o parse_param.o \
|
|
parse_relation.o parse_target.o parse_type.o parse_utilcmd.o scansup.o
|
|
|
|
FLEXFLAGS = -CF
|
|
|
|
include $(top_srcdir)/src/backend/common.mk
|
|
|
|
|
|
# scan is compiled as part of gram
|
|
gram.o: scan.c
|
|
|
|
# Latest flex causes warnings in this file.
|
|
ifeq ($(GCC),yes)
|
|
gram.o: CFLAGS += -Wno-error
|
|
endif
|
|
|
|
|
|
# There is no correct way to write a rule that generates two files.
|
|
# Rules with two targets don't have that meaning, they are merely
|
|
# shorthand for two otherwise separate rules. To be safe for parallel
|
|
# make, we must chain the dependencies like this. The semicolon is
|
|
# important, otherwise make will choose the built-in rule for
|
|
# gram.y=>gram.c.
|
|
|
|
gram.h: gram.c ;
|
|
|
|
gram.c: gram.y
|
|
ifdef BISON
|
|
$(BISON) -d $(BISONFLAGS) -o $@ $<
|
|
else
|
|
@$(missing) bison $< $@
|
|
endif
|
|
|
|
|
|
scan.c: scan.l
|
|
ifdef FLEX
|
|
$(FLEX) $(FLEXFLAGS) -o'$@' $<
|
|
else
|
|
@$(missing) flex $< $@
|
|
endif
|
|
|
|
|
|
# Force these dependencies to be known even without dependency info built:
|
|
gram.o keywords.o parser.o: gram.h
|
|
|
|
|
|
# gram.c, gram.h, and scan.c are in the distribution tarball, so they
|
|
# are not cleaned here.
|