Re: concat fails 'sometimes' on empty colums in select

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Stefan de Konink <skinkie(at)xs4all(dot)nl>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: concat fails 'sometimes' on empty colums in select
Date: 2004-12-11 20:04:43
Message-ID: 20041211200443.GA42436@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Dec 11, 2004 at 01:54:35PM -0600, Bruno Wolff III wrote:
>
> Empty strings and NULL values aren't the same thing. You probably either
> want to store empty strings or use coalesce to change NULL to an empty
> string before using concatenation, as a NULL concatenated with anything
> results in NULL.

To simplify this operation you could create an operator that does
the coalesce for you. This has come up recently; search the list
archives for examples.

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Fuhr 2004-12-12 01:55:57 Re: create/drop table bug
Previous Message Bruno Wolff III 2004-12-11 19:54:35 Re: concat fails 'sometimes' on empty colums in select