Bug #638: Buggy select statment with numeric

From: pgsql-bugs(at)postgresql(dot)org
To: pgsql-bugs(at)postgresql(dot)org
Subject: Bug #638: Buggy select statment with numeric
Date: 2002-04-22 12:21:20
Message-ID: 20020422122120.CED64475484@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Florian Steffen (mailing-list(at)urbanet(dot)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

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2002-04-22 12:28:02 Bug #639: JDBC interface, ResultSet.getObject on with an array of char is crashing.
Previous Message Gerhard Häring 2002-04-22 06:21:30 Re: Escaping of special characters in ARRAYs is broken