Re: why the need for is null?

From: "Chris Travers" <chris(at)travelamericas(dot)com>
To: "Christopher Browne" <cbbrowne(at)acm(dot)org>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: why the need for is null?
Date: 2004-01-05 02:54:50
Message-ID: 00c301c3d33a$0fdab060$af44053d@winxp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Doug McNaught 2004-01-05 03:01:35 Re: PostgreSQL 7.4.1 incredibly slow :-(
Previous Message Carlos Moreno 2004-01-05 02:50:30 Re: PostgreSQL 7.4.1 incredibly slow :-(