On Wed, 6 Jun 2001, Tom Lane wrote:
> Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
> > Yes, column = NULL should *never* return true according to the spec (it
> > should always return NULL in fact as stated). The reason for breaking
> > with the spec is AFAIK to work with broken microsoft clients that seem to
> > think that =NULL is a meaningful test and generate queries using that.
> Microsoft Access is the guilty party, IIRC. I recently tried to stir up
> some interest in changing this behavior back to the standard, but
> apparently there are still too many people using broken versions of
> 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.
Is the conversion just the hack in the grammar rules for
a_expr '=' a_expr?
In response to
pgsql-hackers by date
|Next:||From: Hannu Krosing||Date: 2001-06-07 03:43:36|
|Subject: Any time estimates for 7.1.2 RPM's ?|
|Previous:||From: Hannu Krosing||Date: 2001-06-07 03:09:18|
|Subject: Re: ORDER BY Problem...|
pgsql-sql by date
|Next:||From: Gerald Gutierrez||Date: 2001-06-07 06:10:35|
|Subject: Are SQL commands "atomic" ?|
|Previous:||From: Paul Tomblin||Date: 2001-06-07 02:26:01|
|Subject: Help me speed things up...|