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... :-)
Mike Mascari
mascarm@mascari.com
-----Original Message-----
From: Tom Ivar Helbekkmo [SMTP:tih@kpnQwest.no]
Sent: Thursday, June 07, 2001 3:18 PM
To: Tom Lane
Cc: Stephan Szabo; Mark Stosberg; pgsql-sql@postgresql.org;
pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Re: [SQL] behavior of ' = NULL' vs. MySQL vs.
Standards
Tom Lane <tgl@sss.pgh.pa.us> writes:
> A compromise answer might be to offer a SET variable that selects
the
> Microsoft-compatible misimplementation. Would that fly?
I'd say that's the best way to handle stuff like this. If you
implement something that breaks the standard, to be compatible with
arrogant programmers at Microsoft who feel that they are above such
things, you're encouraging users to develop bad habits. Better to
make them go "SET MICROSOFT BUG COMPATIBILITY ON" first.
To see the effect of leniency in re standards, just try to browse
around the web with a browser that rejects incorrect HTML! :-)