X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id DB4C6D1E84A for ; Tue, 20 Jan 2004 16:38:13 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 62637-08 for ; Tue, 20 Jan 2004 12:37:41 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 11AE4D1E3D2 for ; Tue, 20 Jan 2004 12:37:41 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i0KGbeU6052781 for ; Tue, 20 Jan 2004 16:37:40 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i0KGCZlQ049531 for pgsql-sql@postgresql.org; Tue, 20 Jan 2004 16:12:35 GMT From: Christopher Browne X-Newsgroups: comp.databases.postgresql.sql Subject: Re: comparing nulls Date: Tue, 20 Jan 2004 11:06:51 -0500 Organization: cbbrowne Computing Inc Lines: 18 Message-ID: References: <04012019131206.01434@thenilgiris.com> <1074607016.49673.23.camel@morpheus.hub.org> <04012019542108.01434@thenilgiris.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Reasonable Discussion, linux) Cancel-Lock: sha1:yKbSRGtMlYFbWrdZVoic0OdnHGc= To: pgsql-sql@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/188 X-Sequence-Number: 16581 Centuries ago, Nostradamus foresaw when lawgon@thenilgiris.com (Kenneth Gonsalves) would write: > On Tuesday 20 January 2004 19:26, Chris Bowlby wrote: >> Under 7.3.x this option was removed, you need to test via: >> >> SELECT * from table where field IS NULL; > thanx - works in both 7.1 and 7.3 - why do these guys keep fooling around > with these thangs? Because there is a desire to have PostgreSQL conform with public standards such as SQL-1999. The use of "IS NULL" conforms with SQL standards; the use of "= NULL" does not. -- If this was helpful, rate me http://www3.sympatico.ca/cbbrowne/advocacy.html "Let's face it -- ASCII text is a far richer medium than most of us deserve." -- Scott McNealy