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

From Asfand Qazi (Sanger Institute)
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
Msg-id BANLkTimQa520c-QdA8dLVzVsAqz-5V3gVA@mail.gmail.com
Whole thread Raw
In response to Re: In a view, how do I cause fields with possible NULLs to be treated as a blank string in a replace operation?  (Rick Genter <rick.genter@gmail.com>)
List pgsql-general
On Mon, Jun 27, 2011 at 5:58 PM, Thom Brown <thom@linux.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.genter@gmail.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

pgsql-general by date:

Previous
From: "David Johnston"
Date:
Subject: Re: OFF-TOPIC Gist Index: Problem getting data in GiST Support Functions "penalty".
Next
From: Wim Bertels
Date:
Subject: Re: CRUD plpgsql generator