Re: Bug #604: string join problem

Поиск
Список
Период
Сортировка
От Erol Ozcan
Тема Re: Bug #604: string join problem
Дата
Msg-id 3C7BB972.77F1E304@infotron.com.tr
обсуждение исходный текст
Ответ на Bug #604: string join problem  (pgsql-bugs@postgresql.org)
Список pgsql-bugs
Tom Lane wrote:

> pgsql-bugs@postgresql.org writes:
> > I have a major problem with string joining in sql query in Postgresql 7.1.3. It is always return null string if any
ofcolumn has null value. 
>
> This is not a bug.  SQL92 6.13 general rule 2a saith:
>
>             a) If either S1 or S2 is the null value, then the result of the
>               <concatenation> is the null value.
>
> Consider using something like
>
>         COALESCE(col1,'') || COALESCE(col2,'') || ...
>
> if you want to treat NULLs as empty strings.  Also consider whether you
> shouldn't have stored the fields as empty strings in the first place.
> NULL and empty string are not at all the same thing; if your data design
> treats them as interchangeable then your design is broken, IMHO.
>
>                         regards, tom lane

Thanks for the reply. COALESCE is working good, however,  I wrote a PL/pgSQL procedure to get more proper results.

Best Regards,
--
==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+==
Erol Ozcan                    mailto:erol@infotron.com.tr
Software Engineer         http://www.infotron.com.tr
                                     Tel: +90-216-4921002
info(+)TRON  A.S                 Istanbul/Turkey
==+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+==

В списке pgsql-bugs по дате отправления:

Предыдущее
От: toxic
Дата:
Сообщение: problems with configure connected with readline&history
Следующее
От: Tom Lane
Дата:
Сообщение: Re: COPY FROM is not 8bit clean