Re: (PATCH) Adding CORRESPONDING (NULL error)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kerem Kat <keremkat(at)gmail(dot)com>
Cc: Erik Rijkers <er(at)xs4all(dot)nl>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: (PATCH) Adding CORRESPONDING (NULL error)
Date: 2011-10-27 19:55:57
Message-ID: 4746.1319745357@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kerem Kat <keremkat(at)gmail(dot)com> writes:
> Union with NULL error persists without the corresponding patch. Here
> is the output from postgres without the patch:

> SELECT a FROM (SELECT 1 a) foo
> UNION
> SELECT a FROM (SELECT NULL a) foo2;

> ERROR: failed to find conversion function from unknown to integer

Yeah, this is a longstanding issue that is not simple to fix without
introducing other unpleasantnesses. It is not something you should
try to deal with at the same time as implementing CORRESPONDING.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-10-27 20:20:55 Re: (PATCH) Adding CORRESPONDING (NULL error)
Previous Message Robert Haas 2011-10-27 19:49:50 fun with unlogged tables