Skip site navigation (1) Skip section navigation (2)

Re: problem with new postgresql driver

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: awais <awais(at)techlogix(dot)com>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: problem with new postgresql driver
Date: 2002-03-14 15:33:41
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Thu, 14 Mar 2002, awais wrote:

> 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 more than 1) of "atm" table have this column value set as
> (null). When we executed the query "select * from atm where
> location=null ", 0 rows were returned, which was not we were
> expecting.

This is the correct behavior.  The test you want is really where
location IS NULL.  The older versions had a hack to allow
=NULL be transformed into IS NULL due to some broken clients which
is now turned off by default.

You can use set transform_null_equals=true to get back the old behavior.

In response to

pgsql-bugs by date

Next:From: pgsql-bugsDate: 2002-03-14 16:22:10
Subject: Bug #615: Bug in ilke and ~~* Sql expression
Previous:From: bgrimmDate: 2002-03-14 15:29:18
Subject: Re: Bug #613: Sequence values fall back to previously chec

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group