pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thomas Lockhart <lockhart@fourpalms.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephan Szabo <sszabo@megazone23.bigpanda.com>
Cc: Mark Stosberg <mark@summersault.com>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: behavior of ' = NULL' vs. MySQL vs. Standards
Date: Thu, 07 Jun 2001 13:41:32 +0000
Message-ID: <3B1F848C.CAA0F438@fourpalms.org> (raw)
References: <Pine.BSF.4.21.0106061809050.18346-100000@megazone23.bigpanda.com>
	<6689.991880382@sss.pgh.pa.us>

> > Yes, column = NULL should *never* return true according to the spec (it
> > should always return NULL in fact as stated).  The reason for breaking
> > with the spec is AFAIK to work with broken microsoft clients that seem to
> > think that =NULL is a meaningful test and generate queries using that.
> Microsoft Access is the guilty party, IIRC.  I recently tried to stir up
> some interest in changing this behavior back to the standard, but
> apparently there are still too many people using broken versions of
> Access.

Since according to the standard "column = NULL" is a near-useless
construct (equivalent to "FALSE") it does not seem to pollute the
grammar much to allow an M$ compatible interpretation. I was not happy
having it added (much better to ask that responsive, customer-focused
company to fix their language compliance) but now that it is there it
seems to be an isolated and manageable feature.

                      - Thomas



view thread (17+ messages)  latest in thread

Message-ID: <3B1F848C.CAA0F438@fourpalms.org>
Permalink:  ../3B1F848C.CAA0F438@fourpalms.org/
Also on:    postgresql.org/message-id/3B1F848C.CAA0F438@fourpalms.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: lockhart@fourpalms.org, tgl@sss.pgh.pa.us, sszabo@megazone23.bigpanda.com, mark@summersault.com, pgsql-hackers@postgresql.org
  Subject: Re: behavior of ' = NULL' vs. MySQL vs. Standards
  In-Reply-To: <3B1F848C.CAA0F438@fourpalms.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox