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

Re: comparing nulls

From: Jeff Eckermann <jeff_eckermann(at)yahoo(dot)com>
To: Kenneth Gonsalves <lawgon(at)thenilgiris(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: comparing nulls
Date: 2004-01-20 15:53:41
Message-ID: 20040120155341.70533.qmail@web20807.mail.yahoo.com (view raw or flat)
Thread:
Lists: pgsql-sql
--- Guy Fraser <guy(at)incentre(dot)net> wrote:
> Kenneth Gonsalves wrote:
> 
> >On Tuesday 20 January 2004 19:26, Chris Bowlby
> wrote:
> >  
> >
> >>Hi Ken,
> >>
> >> Under 7.3.x this option was removed, you need to
> test via:
> >>
> >> SELECT * from table where field IS NULL;
> >>    
> >>
> >thanx - works in both 7.1 and 7.3 - why do these
> guys keep fooling around 
> >with these thangs?
> >  
> >
> Standards compliance :-)

You can get the old behaviour by setting
"transform_null_equals" to true in postgresql.conf. 

I believe that this was originally added to add
compatibility with MS Access.  But Access no longer
requires this, and the developers were not interested
in maintaining a non-spec-compliant behaviour.  But
the postgresql.conf setting was retained for those who
have code that relies on that behaviour.

__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus

In response to

pgsql-sql by date

Next:From: Tom LaneDate: 2004-01-20 15:58:04
Subject: Re: Fetching a single column from a record returning function
Previous:From: Guy FraserDate: 2004-01-20 15:28:51
Subject: Re: comparing nulls

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