From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephan Szabo <sszabo@megazone23.bigpanda.com>
Cc: Mark Stosberg <mark@summersault.com>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: behavior of ' = NULL' vs. MySQL vs. Standards
Date: Thu, 07 Jun 2001 06:00:30 -0400
Message-ID: <7323.991908030@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.BSF.4.21.0106062007340.18894-100000@megazone23.bigpanda.com>
References: <Pine.BSF.4.21.0106062007340.18894-100000@megazone23.bigpanda.com>
Stephan Szabo <sszabo@megazone23.bigpanda.com> writes:
>> A compromise answer might be to offer a SET variable that selects the
>> Microsoft-compatible misimplementation. Would that fly?
> It would for me. I'd rather have the default be the spec correct behavior
> and let people configure their server to follow the misinterpretation.
Yes, I agree.
> Is the conversion just the hack in the grammar rules for
> a_expr '=' a_expr?
AFAIK that's it. It might be a little tricky to do cleanly,
though, since gram.y shouldn't look at SET vars. Really, the
conversion would have to be done in analyze.c instead.
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, sszabo@megazone23.bigpanda.com, mark@summersault.com, pgsql-hackers@postgresql.org
Subject: Re: behavior of ' = NULL' vs. MySQL vs. Standards
In-Reply-To: <7323.991908030@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