Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f572L3E24452; Wed, 6 Jun 2001 22:21:03 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f572JgR06692; Wed, 6 Jun 2001 22:19:42 -0400 (EDT) To: Stephan Szabo cc: Mark Stosberg , pgsql-sql@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: behavior of ' = NULL' vs. MySQL vs. Standards In-reply-to: References: Comments: In-reply-to Stephan Szabo message dated "Wed, 06 Jun 2001 18:12:51 -0700" Date: Wed, 06 Jun 2001 22:19:42 -0400 Message-ID: <6689.991880382@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/91 X-Sequence-Number: 3310 Stephan Szabo writes: > 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. A compromise answer might be to offer a SET variable that selects the Microsoft-compatible misimplementation. Would that fly? regards, tom lane