> A select statement with a where clause on a numeric column tested
> for equality against null always return empty result.
This is correct behavior per SQL9x standards. NULL is *not* a value, but
represents the absense of information so tests FALSE in comparisons of
any kind.
hth
[EMAIL PROTECTED] writes:
>> select * from t where n ISNULL;
> n | s
> ---+--
>| asdasdasd
>|
> (2 rows)
>> select * from t where n=NULL;
> n | s
> ---+---
> (0 rows)
This is not a bug.
However, you can make 7.2 work in that braindead Microsoft-compatible
On Mon, 22 Apr 2002 [EMAIL PROTECTED] wrote:
> Florian Steffen ([EMAIL PROTECTED]) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Short Description
> Buggy select statment with numeric
>
> Long Description
> A select statement with a where clause on a numeri
Florian Steffen ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
Buggy select statment with numeric
Long Description
A select statement with a where clause on a numeric column tested
for equality against null always return empt
