Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f58ErPE19975 for ; Fri, 8 Jun 2001 10:53:25 -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 f58Er5R09630; Fri, 8 Jun 2001 10:53:05 -0400 (EDT) To: "Josh Berkus" cc: pgsql-sql@postgresql.org Subject: Re: behavior of ' = NULL' vs. MySQL vs. Standards In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Thu, 07 Jun 2001 08:53:21 -0700" Date: Fri, 08 Jun 2001 10:53:05 -0400 Message-ID: <9627.992011985@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/122 X-Sequence-Number: 3342 "Josh Berkus" writes: >> Microsoft Access is the guilty party, IIRC. > Which verison? I work with MSAccess 97 a lot, and the supported syntax > is "IS NULL". In our last go-round on this (pghackers around 14 Jan 2001), Mike Mascari wrote: : I don't have Office 2000, but I can confirm Access 97 generates such : queries. The query-builder doesn't generate the 'key = NULL' query, but the : use of the Forms interface does. regards, tom lane