| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Sam Mason <sam(at)samason(dot)me(dot)uk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: handling of COUNT(record) vs IS NULL |
| Date: | 2008-01-28 21:38:01 |
| Message-ID: | 7621.1201556281@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Sam Mason <sam(at)samason(dot)me(dot)uk> writes:
> I've just noticed that the handling of COUNT(record) and (record IS
> NULL) aren't consistent with my understanding of them. If I run the
> following query:
> SELECT
> NULL IS NULL, COUNT( NULL ),
> (NULL,NULL) IS NULL, COUNT((NULL,NULL));
> The IS NULL checks both return TRUE as I'd expect them to, but the
> second count doesn't return 0.
THe fourth of those isn't really valid SQL. According to SQL99,
IS NULL takes a <row value expression> as argument, so it's valid
to do (NULL,NULL) IS NULL, but COUNT takes a <value expression>.
I don't see anything in the spec suggesting that we are supposed
to drill down into a rowtype value to see whether all its fields
are null, in any context other than the IS [NOT] NULL predicate.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vlad | 2008-01-28 21:56:20 | 8.3RC2 vs 8.2.6 testing results |
| Previous Message | Tom Lane | 2008-01-28 21:13:24 | Re: Surprising (?) Sequence Behavior |