Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f57A1WE28610; Thu, 7 Jun 2001 06:01:32 -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 f57A0UR07326; Thu, 7 Jun 2001 06:00:30 -0400 (EDT) To: Stephan Szabo cc: Mark Stosberg , pgsql-sql@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: behavior of ' = NULL' vs. MySQL vs. Standards In-reply-to: References: Comments: In-reply-to Stephan Szabo message dated "Wed, 06 Jun 2001 20:12:46 -0700" Date: Thu, 07 Jun 2001 06:00:30 -0400 Message-ID: <7323.991908030@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/96 X-Sequence-Number: 3315 Stephan Szabo 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