Re: Update on Access 97 and = NULL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mike Mascari <mascarm(at)mascari(dot)com>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Update on Access 97 and = NULL
Date: 2001-06-14 23:18:26
Message-ID: 23142.992560706@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Mike Mascari <mascarm(at)mascari(dot)com> writes:
> However, I did find this
> explanation as to why on the Microsoft Knowledge Base:

> http://support.microsoft.com/support/kb/articles/Q237/9/92.ASP

Interesting. Apparently, at this point our "Microsoft-compatible"
hack is arguably *failing* to be Microsoft-compatible.

The KB article is carefully written to make it sound like the only
"foo = NULL" queries out there are mistakes made by users; but wasn't
the original issue that Access97 itself would generate a bogus query?

I'm confused about which component is what here ... what exactly is
the relationship between Access, Jet, MDAC, etc?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Myers 2001-06-14 23:20:46 Re: What (not) to do in signal handlers
Previous Message Bruce Momjian 2001-06-14 23:05:10 Re: [PATCH] indexability of << operator for inet/cidr