Re: NULL value in subselect in UNION causes error - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: NULL value in subselect in UNION causes error
Date
Msg-id [email protected]
Whole thread Raw
In response to Re: NULL value in subselect in UNION causes error  (Tom Lane <[email protected]>)
List pgsql-hackers
On 1/26/2007 3:41 PM, Tom Lane wrote:
> Jan Wieck <[email protected]> writes:
>> Checked it against HEAD and 8.2:
>> postgres=# select 1, 1, 1 union select * from (select 2, null, 2) two;
>> ERROR:  failed to find conversion function from "unknown" to integer
> 
> It's always done that.   The SQL spec would tell you that you have to
> cast the null to some specific type.  We allow untyped nulls in contexts
> where we can derive a type from reasonably nearby context, but an
> integer two levels up and over in another union arm isn't very nearby
> IMHO.  So I'm not particularly concerned about making this work ...

That explains. Thanks.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== [email protected] #


pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Recursive query syntax ambiguity
Next
From: Martijn van Oosterhout
Date:
Subject: Re: VC2005 build and pthreads