Commit8964b41

Neil Conway

committed

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

established: referencing an undefined parameter should result in anerror, not NULL.

1 parent9b3aee5 commit8964b41Copy full SHA for 8964b41

File tree

-6

lines changed

-6

lines changed

Lines changed: 1 addition & 6 deletions

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

Comments

(0)