Re: behavior of ' = NULL' vs. MySQL vs. Standards

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Josh Berkus" <josh(at)agliodbs(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: behavior of ' = NULL' vs. MySQL vs. Standards
Date: 2001-06-08 14:53:05
Message-ID: 9627.992011985@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-sql

"Josh Berkus" <josh(at)agliodbs(dot)com> writes:
>> Microsoft Access is the guilty party, IIRC.

> Which verison? I work with MSAccess 97 a lot, and the supported syntax
> is "IS NULL".

In our last go-round on this (pghackers around 14 Jan 2001),
Mike Mascari wrote:

: I don't have Office 2000, but I can confirm Access 97 generates such
: queries. The query-builder doesn't generate the 'key = NULL' query, but the
: use of the Forms interface does.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Philip Crotwell 2001-06-08 14:55:45 unlink large objects
Previous Message Robert Forsman 2001-06-08 14:52:37 7.1.2 RPMs

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2001-06-08 15:04:26 Re: [HACKERS] Re: behavior of ' = NULL' vs. MySQL vs. Standards
Previous Message Tom Lane 2001-06-08 14:41:22 Re: Re: [SQL] maximum number of rows in table - what about oid limits?