Oddities with NULL and GROUP BY

From: secret <secret(at)kearneydev(dot)com>
To: PG-SQL <pgsql-sql(at)postgresql(dot)org>
Subject: Oddities with NULL and GROUP BY
Date: 1999-05-14 16:57:37
Message-ID: 373C5600.89E98420@kearneydev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Maybe there is something I don't know about how GROUP BY should
work, but if I have a table like:
a,b,c
1,1,1
1,1,2
1,1,3
1,2,1
1,3,1

And I say SELECT a,b,sum(c) FROm .. GROUP BY a,b I get
1,1,6
1,2,1
1,3,1

So whenever a or b changes we get a new summed row, well if I have rows
where a or b are null, this doesn't happen, infact I seem to get all
those rows individually... Like if:
1,1,1
1,1,3
1,NULL,10
1,NULL,20
1,2,3

I get:
1,1,4
1,NULL,10
1,NULL,20
1,2,3

Shouldn't I get 1,NULL,30? Ie shouldn't NULL be treated like any other
value? Or is there some bit of information I'm missing? I can set
everything from NULL to 0 if need be, but I'd rather not...

David Secret
MIS Director
Kearney Development Co., Inc.

Browse pgsql-sql by date

  From Date Subject
Next Message Doug Younger 1999-05-14 17:36:33 Create Rule problems
Previous Message Tom Lane 1999-05-14 00:14:26 Re: [SQL] JOIN index/sequential select problem