From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'Tom Ivar Helbekkmo'" <tih(at)kpnQwest(dot)no> |
Cc: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | AW: AW: Re: [SQL] behavior of ' = NULL' vs. MySQL vs. S tand ards |
Date: | 2001-06-07 11:38:46 |
Message-ID: | 11C1E6749A55D411A9670001FA687963368313@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > Actually I am not sure whether the column = NULL syntax is even defined
> > or allowed in SQL92 (e.g. Informix interprets the NULL as column name in
> > this context and errs out).
>
> I don't have the standard handy, but I do have Joe Celko's book, "Data
> & Databases: Concepts in Practice". He says (in section 8.2, under
> the heading "Multivalued Logic"):
>
> A NULL cannot be compared to another NULL or to a value
I mean that I am not sure NULL is a valid constant in a where clause
comparison.
Thus it could be, that NULL in "where column = NULL" is not defined
to have a special meaning according to SQL92.
NULL is probably only defined in a special context, like:
IS NULL
IS NOT NULL
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | mlw | 2001-06-07 12:03:55 | Re: Acucobol interface |
Previous Message | mlw | 2001-06-07 11:36:41 | Re: 7.2 items |