From: | "Bob Pawley" <rjpawley(at)shaw(dot)ca> |
---|---|
To: | "Sam Mason" <sam(at)samason(dot)me(dot)uk>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Adding a null |
Date: | 2009-11-05 21:19:53 |
Message-ID: | 6C6D7EF5EBDB4CA7A37E54CE871C54DE@desktop |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks Sam
Worked perfectly.
Bob
----- Original Message -----
From: "Sam Mason" <sam(at)samason(dot)me(dot)uk>
To: <pgsql-general(at)postgresql(dot)org>
Sent: Thursday, November 05, 2009 10:28 AM
Subject: Re: [GENERAL] Adding a null
> On Thu, Nov 05, 2009 at 10:13:28AM -0800, Bob Pawley wrote:
>> However one variable sometimes returns a null value which invariably
>> gives a null answer.
>>
>> How can I work around this??
>
> What do you want it to do with the NULL value? I'm assuming you want to
> use COALESCE, something like:
>
> COALESCE(n,0) + COALESCE(m,0)
>
> --
> Sam http://samason.me.uk/
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2009-11-05 21:23:04 | Re: postgres logs indicate errors with prepared statements, since pgbouncer was installed. |
Previous Message | Vick Khera | 2009-11-05 20:49:29 | Re: Bench marking performance or experience using Solid State Disk Drives (SSD) with postgres |