Re: Avoid casting NULLs in UNION... - Mailing list pgsql-admin

From Albe Laurenz
Subject Re: Avoid casting NULLs in UNION...
Date
Msg-id A737B7A37273E048B164557ADEF4A58B057AE08C@ntex2010a.host.magwien.gv.at
Whole thread Raw
In response to Avoid casting NULLs in UNION...  (Marko Rihtar <rihtar.marko@gmail.com>)
Responses Re: Avoid casting NULLs in UNION...  (Marko Rihtar <rihtar.marko@gmail.com>)
List pgsql-admin
Marko Rihtar wrote:
> maybe you can help me with this issue.
> Here is an example
>
> SELECT NULL::integer
> UNION ALL
> SELECT NULL
> UNION ALL
> SELECT 123
>
> For this sql to work i have to cast NULL to integer.
> I was wondering if there exists some configuration parameter at database level that can be used to
> avoid this need for explicit casting?

Not that I know of.

The behaviour is well defined and documented, see
http://www.postgresql.org/docs/current/static/typeconv-union-case.html

The UNIONs are computed left to right,
and the data type in the first UNION resolves to "text"
according to rule 2 of the page given above.

You can reorder the UNIONs or use parentheses.

Yours,
Laurenz Albe


pgsql-admin by date:

Previous
From: Marko Rihtar
Date:
Subject: Avoid casting NULLs in UNION...
Next
From: Raju Angani
Date:
Subject: Zabbix Postbix help