From: | "Vincent Hikida" <vhikida(at)inreach(dot)com> |
---|---|
To: | "Bruno Wolff III" <bruno(at)wolff(dot)to> |
Cc: | <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: + operator with a possible NULL operand |
Date: | 2003-05-29 20:32:09 |
Message-ID: | 022b01c32621$60ece520$6601a8c0@HOMEOFFICE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
You're right of course!! Small glitch in my program but I think it's been
debugged now.
Sorry, ... I just got back from seeing the Matrix.
Vincent Hikida,
Member of Technical Staff - Urbana Software, Inc.
"A Personalized Learning Experience"
----- Original Message -----
From: "Bruno Wolff III" <bruno(at)wolff(dot)to>
To: "Vincent Hikida" <vhikida(at)inreach(dot)com>
Cc: "Michael Glaesemann" <grzm(at)myrealbox(dot)com>; <pgsql-novice(at)postgresql(dot)org>
Sent: Thursday, May 29, 2003 4:16 AM
Subject: Re: [NOVICE] + operator with a possible NULL operand
> On Wed, May 28, 2003 at 23:43:19 -0700,
> Vincent Hikida <vhikida(at)inreach(dot)com> wrote:
> >
> > That is
> >
> > SELECT SUM(numvar) FROM tablex
> >
> > Will treat any numvar which are null as if they were a zero. However,
the
> > following will not treat it as zero but non-existent.
>
> Aggragates (except for count(*)) will skip any row for which the
expression
> is null. For sum() that turns out to be equivalent to treating the number
> as zero because of the way math works. But the function isn't actually
> treating nulls as zeros.
>
From | Date | Subject | |
---|---|---|---|
Next Message | M. Bastin | 2003-05-29 21:07:26 | MD5 done. Thanks! |
Previous Message | M. Bastin | 2003-05-29 17:42:17 | MD5 different standards--or not? |