Re: strange behaviour

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Mathieu Arnold <mat(at)mat(dot)cc>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: strange behaviour
Date: 2001-02-25 13:33:56
Message-ID: Pine.LNX.4.30.0102251430160.752-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Mathieu Arnold writes:

> sympa=> select count(*) from subscriber_table;
> count
> -------
> 14029
> sympa=> select count(*) from subscriber_table where bounce_subscriber = NULL;
> count
> -------
> 14024
> sympa=> select count(*) from subscriber_table where bounce_subscriber <> NULL;
> count
> -------
> 0

'anything <> NULL' can never be true, because 'anything {operator} NULL'
is always NULL, which means false in a WHERE clause. The reason that
'anything = NULL' works is that it is explicitly handled to work around MS
Access breakage. What you want to use is 'xxx IS NULL' and 'xxx IS NOT
NULL'.

> sympa=> select count(*) from subscriber_table where bounce_subscriber = '';
> count
> -------
> 0
> sympa=> select count(*) from subscriber_table where bounce_subscriber <> '';
> count
> -------
> 5
>
> I was thinking that "= NULL" and "<> NULL" were oposite and that "<> NULL"
> would give me the result i had with "<> ''" or am I mistaken ?

NULL and '' are not the same, in spite of anything Oracle is trying to
tell you.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Uro Gruber 2001-02-25 15:32:22 PHP4.0.4pl1 and PostgreSQL 7.1beta4
Previous Message Mathieu Arnold 2001-02-25 12:37:15 strange behaviour