Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f58M1jE91947 for ; Fri, 8 Jun 2001 18:01:45 -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 f58M1fR12215; Fri, 8 Jun 2001 18:01:41 -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 "Fri, 08 Jun 2001 08:33:07 -0700" Date: Fri, 08 Jun 2001 18:01:41 -0400 Message-ID: <12212.992037701@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/135 X-Sequence-Number: 3356 "Josh Berkus" writes: >> : 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. > As someone who develops professionally for MSAccess<->ODBC Servers > (PostgreSQL and MS SQL Server) I'd say that we can ignore this. There > are a *lot* of circumstances where the "Filter by Form" interface breaks > down; I don't think that it works properly with MS SQL Server 7.0, > either. This is an interesting comment. Does anyone else want to confirm or refute it? If Access' forms interface is so badly broken that few people use it anyway, then I'd say that we should not break standards compatibility just to support it. regards, tom lane