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 22:01:41 |
Message-ID: | 12212.992037701@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:
>> : 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.
> As someone who develops professionally for MSAccess<->ODBC Servers
> (PostgreSQL and MS SQL Server) I'd say that we can ignore this. There
> are a *lot* of circumstances where the "Filter by Form" interface breaks
> down; I don't think that it works properly with MS SQL Server 7.0,
> either.
This is an interesting comment. Does anyone else want to confirm or
refute it? If Access' forms interface is so badly broken that few
people use it anyway, then I'd say that we should not break standards
compatibility just to support it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-06-08 22:14:54 | Re: Re: AW: Re: [SQL] behavior of ' = NULL' vs. MySQL vs. Stand ards |
Previous Message | Tom Lane | 2001-06-08 21:55:14 | Re: Is this a bug? |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2001-06-08 22:03:15 | Re: maximum number of rows in table - what about oid limits? |
Previous Message | Jonathan Bartlett | 2001-06-08 21:42:09 | Re: maximum number of rows in table - what about oid limits? |