| From: | Tom Ivar Helbekkmo <tih(at)kpnQwest(dot)no> |
|---|---|
| To: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
| 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: | Re: AW: AW: Re: [SQL] behavior of ' = NULL' vs. MySQL vs. S tand ards |
| Date: | 2001-06-07 12:46:50 |
| Message-ID: | 86snhcpidh.fsf@athene.i.eunet.no |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> writes:
> Thus it could be, that NULL in "where column = NULL" is not defined
> to have a special meaning according to SQL92.
The way I interpret Celko's interpretation of SQL92, that specific
construct has a meaning; it evaluates to UNKNOWN, thus not to TRUE,
and the WHERE clause becomes useless, as does any other combination of
a theta operator and the explicit constant 'NULL'. This is almost,
but not quite, an argument for allowing "= NULL" for "IS NULL". ;-)
Does anyone out there have the actual text of the standard?
-tih
--
The basic difference is this: hackers build things, crackers break them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergio Bruder | 2001-06-07 12:53:04 | Re: Any time estimates for 7.1.2 RPM's ? |
| Previous Message | Jim Mercer | 2001-06-07 12:39:47 | Re: PQgetvalue: ERROR! tuple number 0 is out of range 0..-1 |