From: | Russell Smith <mr-russ(at)pws(dot)com(dot)au> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #1677: Bug in select with Union |
Date: | 2005-05-24 08:56:22 |
Message-ID: | 200505241856.22936.mr-russ@pws.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, 23 May 2005 11:54 pm, Tom Lane wrote:
> "Julien Vallet" <julien(dot)vallet(at)density-tech(dot)com> writes:
> > The result is "ERROR: UNION types text and bigint cannot be matched"
>
> This is the identical issue reported here:
> http://archives.postgresql.org/pgsql-bugs/2005-02/msg00008.php
> See also this thread:
> http://archives.postgresql.org/pgsql-general/2005-02/msg00693.php
>
> The short answer is that what you wrote is illegal per the SQL spec
> (which doesn't allow NULL to be used in ways where a type can't be
> ascribed immediately). While we'd like to accept it, we have
> not figured out a rule that doesn't break the spec in other ways.
> For now I'd recommend casting the NULLs explicitly.
Can we spit out an error that is slightly more relevant? Maybe print
a warning/error that NULL was used without a type?
Regards
Russell Smith
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Szűcs Gábor | 2005-05-24 10:39:04 | Re: could not devise a query plan |
Previous Message | Neil Conway | 2005-05-24 06:45:26 | Re: BUG #1671: Long interval string representation rejected |