Message-ID: <20040120155341.70533.qmail@web20807.mail.yahoo.com>
Date: Tue, 20 Jan 2004 07:53:41 -0800 (PST)
From: Jeff Eckermann <jeff_eckermann@yahoo.com>
Subject: Re: comparing nulls
To: Kenneth Gonsalves <lawgon@thenilgiris.com>
Cc: pgsql-sql@postgresql.org
In-Reply-To: <400D4933.3030007@incentre.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

--- Guy Fraser <guy@incentre.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