Re: why the need for is null? - Mailing list pgsql-general

From Chris Travers
Subject Re: why the need for is null?
Date
Msg-id 00c301c3d33a$0fdab060$af44053d@winxp
Whole thread Raw
In response to why the need for is null?  (Baldur Norddahl <bbn-pgsql.general@clansoft.dk>)
Responses Re: why the need for is null?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Minor correction to Christopher Browne's post:

It is currently possible to set PostgreSQL to evaluate x = NULL as x IS
NULL.

Under the current documentations section 16.4.9.2. (Platform and Client
Compatibility):

transform_null_equals (boolean)

When turned on, expressions of the form expr = NULL (or NULL = expr) are
treated as expr IS NULL, that is, they return true if expr evaluates to the
null value, and false otherwise. The correct behavior of expr = NULL is to
always return null (unknown). Therefore this option defaults to off.


This option is set in the postgresql.conf file.  Hope this helps.

Best Wishes,
Chris Travers



pgsql-general by date:

Previous
From: "Chris Travers"
Date:
Subject: Re: Installed postgresql 7.4 on Redhat 9.0 but can't run pgcrypto.sql
Next
From: "Octavio Alvarez"
Date:
Subject: History-based (or logged) database.