Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28])
	by postgresql.org (8.11.3/8.11.1) with SMTP id f5CGxJE53636
	for <pgsql-sql@postgresql.org>; Tue, 12 Jun 2001 12:59:19 -0400 (EDT)
	(envelope-from pgsql-sql-owner@postgresql.org)
Received: from athene.i.eunet.no (athene.i.eunet.no [193.71.2.52])
	by postgresql.org (8.11.3/8.11.1) with ESMTP id f57JgZE77815;
	Thu, 7 Jun 2001 15:42:35 -0400 (EDT)
	(envelope-from tih@athene.i.eunet.no)
Received: by athene.i.eunet.no (Postfix, from userid 1001)
	id 6DEDB242C; Thu,  7 Jun 2001 21:42:32 +0200 (CEST)
To: "mascarm@mascari.com" <mascarm@mascari.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
	Stephan Szabo <sszabo@megazone23.bigpanda.com>,
	Mark Stosberg <mark@summersault.com>,
	"pgsql-sql@postgresql.org" <pgsql-sql@postgresql.org>,
	"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] Re: behavior of ' = NULL' vs. MySQL vs. Standards
References: <01C0EF67.9A5733D0.mascarm@mascari.com>
From: Tom Ivar Helbekkmo <tih@kpnQwest.no>
Date: 07 Jun 2001 21:42:32 +0200
In-Reply-To: <01C0EF67.9A5733D0.mascarm@mascari.com> (Mike Mascari's message
	of "Thu, 7 Jun 2001 15:36:20 -0400")
Message-ID: <86snhcm5zr.fsf@athene.i.eunet.no>
Lines: 14
User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Archive-Number: 200106/182
X-Sequence-Number: 3422

Mike Mascari <mascarm@mascari.com> writes:

> The best solution would be to have the ODBC translate instances of '= 
> NULL' into IS NULL before submitting the query to PostgreSQL. I'm 
> sure this is how other vendors, like Oracle handle the issue. Well, 
> probably sure... :-)

<applause>

That's the intelligent solution, of course.

-tih
-- 
The basic difference is this: hackers build things, crackers break them.