problem with new postgresql driver - Mailing list pgsql-bugs

From awais
Subject problem with new postgresql driver
Date
Msg-id 009201c1cb4b$ecc87370$1700a8c0@awais
Whole thread Raw
Responses Re: problem with new postgresql driver
List pgsql-bugs
Hi,

    We have a table named "atm" in our database which is uing latest driver=
 of postgresql, it has a column named "location", all records (which are mo=
re than 1) of "atm" table have this column value set as (null). When we exe=
cuted the query "select * from atm where location=3Dnull ", 0 rows were ret=
urned, which was not we were expecting.

    We have another database using previous driver of postgresql, it also h=
as a table named "atm" with a column named "location", similarly all record=
s (which are more than 1) of "atm" table have this column value set as (nul=
l), when we executed the query "select * from atm where location=3Dnull ", =
all rows were returned, which  was according to our expectations.

    Can u please describe how to tackle this problem.

regards,
Awais

pgsql-bugs by date:

Previous
From: Sridhar Bhamidi
Date:
Subject: Unable to identify an operator '=' for types 'numeric' and 'float8'
Next
From: "Tom Pfau"
Date:
Subject: Re: comparing null value in plpgsql.