Re: In a view, how do I cause fields with possible NULLs to be treated as a blank string in a replace operation?

From: "Asfand Qazi (Sanger Institute)" <aq2(dot)sanger(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: In a view, how do I cause fields with possible NULLs to be treated as a blank string in a replace operation?
Date: 2011-06-28 08:53:08
Message-ID: BANLkTimQa520c-QdA8dLVzVsAqz-5V3gVA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jun 27, 2011 at 5:58 PM, Thom Brown <thom(at)linux(dot)com> wrote:
>
> Try coalesce: http://www.postgresql.org/docs/9.0/static/functions-conditional.html#AEN15541
>
> So if foo is a null value, and you used COALESCE(foo, 'bar'), the
> output would be 'bar', otherwise it would be whatever the value of foo
> is.
>

On Mon, Jun 27, 2011 at 5:59 PM, Rick Genter <rick(dot)genter(at)gmail(dot)com> wrote:
> Either use '' as some_type, or use COALESCE(some_type, '').
>

Thank you both, that worked fine.

--
Regards,
     Asfand Qazi
     Team 87 HTGT
     Wellcome Trust Sanger Institute

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Wim Bertels 2011-06-28 08:54:48 Re: CRUD plpgsql generator
Previous Message David Johnston 2011-06-28 06:26:20 Re: OFF-TOPIC Gist Index: Problem getting data in GiST Support Functions "penalty".