diff options
author | Thomas G. Lockhart <lockhart@fourpalms.org> | 2002-07-04 15:24:11 +0000 |
---|---|---|
committer | Thomas G. Lockhart <lockhart@fourpalms.org> | 2002-07-04 15:24:11 +0000 |
commit | 68d9fbeb5511d846ce3a6f66b8955d3ca55a4b76 (patch) | |
tree | 2c916fdd1c617a90fdd143e6f68ea9c48d19f296 /src/backend/executor/execProcnode.c | |
parent | c7eea66c392cd3f5c914ed135d01a2e20ecb1f92 (diff) | |
download | postgresql-68d9fbeb5511d846ce3a6f66b8955d3ca55a4b76.tar.gz postgresql-68d9fbeb5511d846ce3a6f66b8955d3ca55a4b76.zip |
Implement the IS DISTINCT FROM operator per SQL99.
Reused the Expr node to hold DISTINCT which strongly resembles
the existing OP info. Define DISTINCT_EXPR which strongly resembles
the existing OPER_EXPR opType, but with handling for NULLs required
by SQL99.
We have explicit support for single-element DISTINCT comparisons
all the way through to the executor. But, multi-element DISTINCTs
are handled by expanding into a comparison tree in gram.y as is done for
other row comparisons. Per discussions, it might be desirable to move
this into one or more purpose-built nodes to be handled in the backend.
Define the optional ROW keyword and token per SQL99.
This allows single-element row constructs, which were formerly disallowed
due to shift/reduce conflicts with parenthesized a_expr clauses.
Define the SQL99 TREAT() function. Currently, use as a synonym for CAST().
Diffstat (limited to 'src/backend/executor/execProcnode.c')
0 files changed, 0 insertions, 0 deletions