database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-14 18:42:34 +03:00
Code Activity

Remove a 15-year old comment questioning behavior that is now well-

Browse Source 
established: referencing an undefined parameter should result in an
error, not NULL.
This commit is contained in:
Neil Conway
2006-11-08 00:45:30 +00:00
parent 9b3aee524f
commit 8964b41c7b
1 changed files with 1 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/backend/executor/execQual.c
View File

@ -8,7 +8,7 @@
* *
* *
* IDENTIFICATION * IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/executor/execQual.c,v 1.197 2006/11/06 18:21:31 tgl Exp $ * $PostgreSQL: pgsql/src/backend/executor/execQual.c,v 1.198 2006/11/08 00:45:30 neilc Exp $
* *
*------------------------------------------------------------------------- *-------------------------------------------------------------------------
*/ */
@ -595,11 +595,6 @@ ExecEvalConst(ExprState *exprstate, ExprContext *econtext,
* something like ($.name) and the expression context contains * something like ($.name) and the expression context contains
* the current parameter bindings (name = "sam") (age = 34)... * the current parameter bindings (name = "sam") (age = 34)...
* so our job is to find and return the appropriate datum ("sam"). * so our job is to find and return the appropriate datum ("sam").
*
* Q: if we have a parameter ($.foo) without a binding, i.e.
* there is no (foo = xxx) in the parameter list info,
* is this a fatal error or should this be a "not available"
* (in which case we could return NULL)? -cim 10/13/89
* ---------------------------------------------------------------- * ----------------------------------------------------------------
*/ */
static Datum static Datum