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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-01-20 15:58:04 | Re: Fetching a single column from a record returning function |
Previous Message | Guy Fraser | 2004-01-20 15:28:51 | Re: comparing nulls |