| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
| Cc: | Mark Stosberg <mark(at)summersault(dot)com>, pgsql-sql(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: behavior of ' = NULL' vs. MySQL vs. Standards |
| Date: | 2001-06-07 10:00:30 |
| Message-ID: | 7323.991908030@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Ivar Helbekkmo | 2001-06-07 10:30:20 | Re: AW: Re: [SQL] behavior of ' = NULL' vs. MySQL vs. Stand ards |
| Previous Message | Zeugswetter Andreas SB | 2001-06-07 09:40:22 | AW: Can the backend return more than one error message per PQexec? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | guard | 2001-06-07 10:50:11 | how to configure --with-tcl in CYGWIN |
| Previous Message | David BOURIAUD | 2001-06-07 08:57:06 | About table column names. |