From: Mike Mascari <mascarm@mascari.com>
To: 'Tom Ivar Helbekkmo' <tih@kpnQwest.no>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephan Szabo <sszabo@megazone23.bigpanda.com>
Cc: Mark Stosberg <mark@summersault.com>
Cc: pgsql-sql@postgresql.org <pgsql-sql@postgresql.org>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: RE: [HACKERS] Re: behavior of ' = NULL' vs. MySQL vs. Standards
Date: Thu, 7 Jun 2001 15:36:20 -0400
Message-ID: <01C0EF67.9A5733D0.mascarm@mascari.com> (raw)
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! :-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: mascarm@mascari.com, tih@kpnQwest.no, tgl@sss.pgh.pa.us, sszabo@megazone23.bigpanda.com, mark@summersault.com, pgsql-sql@postgresql.org
Subject: RE: [HACKERS] Re: behavior of ' = NULL' vs. MySQL vs. Standards
In-Reply-To: <01C0EF67.9A5733D0.mascarm@mascari.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox