Re: Avoid casting NULLs in UNION...
| От | Marko Rihtar |
|---|---|
| Тема | Re: Avoid casting NULLs in UNION... |
| Дата | |
| Msg-id | CABSSDoHkQnYRP8yK6p5DDrnF6vo5H56Csw=0suuNsZqJ7acrjA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Avoid casting NULLs in UNION... (Albe Laurenz <laurenz.albe@wien.gv.at>) |
| Список | pgsql-admin |
OK Albe,
thanks for info
thanks for info
2013/2/1 Albe Laurenz <laurenz.albe@wien.gv.at>
Not that I know of.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?
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 по дате отправления: