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

From Marko Rihtar
Subject Re: Avoid casting NULLs in UNION...
Date
Msg-id CABSSDoHkQnYRP8yK6p5DDrnF6vo5H56Csw=0suuNsZqJ7acrjA@mail.gmail.com
Whole thread Raw
In response to Re: Avoid casting NULLs in UNION...  (Albe Laurenz <laurenz.albe@wien.gv.at>)
List pgsql-admin
OK Albe,

thanks for info

2013/2/1 Albe Laurenz <laurenz.albe@wien.gv.at>
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: Dave Manginelli
Date:
Subject: SSPI Authentication on Windows 2012 (for Win. Clients)
Next
From: CS DBA
Date:
Subject: SSL question