Stephan Szabo wrote:
On Thu, 24 Jul 2003, Joe Conway wrote:
I see your point, but mine was that in this case I'd like a NULL
returned and I don't really care about the type. ISTM that NULL should
be able to morph into any type it needs to.
I don't think that's necessarily true.
As a potentially abs
On Thu, 24 Jul 2003, Joe Conway wrote:
> Tom Lane wrote:
> > Joe Conway <[EMAIL PROTECTED]> writes:
> >>So far so good. But look at this one:
> >>regression=# select dwarray(null,null);
> >>ERROR: cannot determine ANYARRAY/ANYELEMENT type because input is UNKNOWN
> >
> > That seems correct to me
Joe Conway <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> We could probably hack the inlining logic to prevent it from inlining
>> the function in this scenario, but I wonder whether this doesn't say
>> that ExecEvalArray is behaving inconsistently. In other operations, any
>> NULL in means NULL
Tom Lane wrote:
Joe Conway <[EMAIL PROTECTED]> writes:
So far so good. But look at this one:
regression=# select dwarray(null,null);
ERROR: cannot determine ANYARRAY/ANYELEMENT type because input is UNKNOWN
That seems correct to me. What would you expect to happen? There's no
type we could assig
Joe Conway <[EMAIL PROTECTED]> writes:
> So far so good. But look at this one:
> regression=# select dwarray(null,null);
> ERROR: cannot determine ANYARRAY/ANYELEMENT type because input is UNKNOWN
That seems correct to me. What would you expect to happen? There's no
type we could assign as the
