Bug #638: Buggy select statment with numeric - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Bug #638: Buggy select statment with numeric
Date
Msg-id 20020422122120.CED64475484@postgresql.org
Whole thread Raw
Responses Re: Bug #638: Buggy select statment with numeric  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
Re: Bug #638: Buggy select statment with numeric  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Florian Steffen (mailing-list@urbanet.ch) 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 empty result. With ISNULL 
everything is fine, but not with the = operator. 

This has been tested on versions 7.1.3 and 7.2.

Sample Code
> create table t (n NUMERIC(39), s TEXT);
CREATE
> insert into t values (NULL, 'asdasdasd');
INSERT 35860 1
> insert into t values (NULL, 'qqqqqqqqqqqq');
INSERT 35861 1
> select * from t where n ISNULL;
 n |      s
---+--------------
   | asdasdasd
   | qqqqqqqqqqqq
(2 rows)

> select * from t where n=NULL;
 n | s
---+---
(0 rows)


No file was uploaded with this report

pgsql-bugs by date:

Previous
From: Gerhard Häring
Date:
Subject: Re: Escaping of special characters in ARRAYs is broken
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #639: JDBC interface, ResultSet.getObject on with an array of char is crashing.