Received: from sss.pgh.pa.us ([192.204.191.242])
	by postgresql.org (8.11.3/8.11.1) with ESMTP id f58F6LE26636;
	Fri, 8 Jun 2001 11:06:21 -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 f58F4QR09682;
	Fri, 8 Jun 2001 11:04:26 -0400 (EDT)
To: "mascarm@mascari.com" <mascarm@mascari.com>
cc: "'Tom Ivar Helbekkmo'" <tih@kpnQwest.no>,
	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 
In-reply-to: <01C0EF67.9A5733D0.mascarm@mascari.com> 
References: <01C0EF67.9A5733D0.mascarm@mascari.com>
Comments: In-reply-to Mike Mascari <mascarm@mascari.com>
	message dated "Thu, 07 Jun 2001 15:36:20 -0400"
Date: Fri, 08 Jun 2001 11:04:26 -0400
Message-ID: <9679.992012666@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200106/123
X-Sequence-Number: 3343

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.

Does Access only talk to Postgres via ODBC?  (Seems plausible, but I
don't know.)  What about people copying-and-pasting queries generated
by Access; is it even possible?

I doubt that this'd really help much, in any case; it merely moves the
necessary switch from the backend to ODBC.

			regards, tom lane