From: Tom Lane <tgl@sss.pgh.pa.us>
To: mascarm@mascari.com <mascarm@mascari.com>
Cc: 'Tom Ivar Helbekkmo' <tih@kpnQwest.no>
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: Fri, 08 Jun 2001 11:04:26 -0400
Message-ID: <9679.992012666@sss.pgh.pa.us> (raw)
In-Reply-To: <01C0EF67.9A5733D0.mascarm@mascari.com>
References: <01C0EF67.9A5733D0.mascarm@mascari.com>
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
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: tgl@sss.pgh.pa.us, mascarm@mascari.com, tih@kpnQwest.no, 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: <9679.992012666@sss.pgh.pa.us>
* 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