Joe Conway <[EMAIL PROTECTED]> writes:
> Here's a patch that replaces the ERROR with a NULL return value when an
> element in an array expression is NULL.
Applied. I also added a comment to remind us to change
contain_nonstrict_functions() when ARRAY's behavior is changed again.
Tom Lane wrote:
Joe Conway <[EMAIL PROTECTED]> writes:
That probably makes good sense, at least until we can deal with NULL
elements. Would that patch count as a bug fix?
Either one would count as a bug fix IMHO. Anyone else have an opinion
on which to do?
Here's a patch that replaces the ERROR w
