| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tod McQuillin <devin(at)spamcop(dot)net> |
| Cc: | Kovacs Baldvin <kb136(at)hszk(dot)bme(dot)hu>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Intentional, or bug? |
| Date: | 2001-09-16 19:31:07 |
| Message-ID: | 18429.1000668667@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Tod McQuillin <devin(at)spamcop(dot)net> writes:
> On Sun, 16 Sep 2001, Kovacs Baldvin wrote:
>> select NULL = NULL;
>>
>> The answer is: true!!!
> This has got to be a bug. NULL is not equal to anything (nor is it
> unequal to anything).
Indeed, this *should* yield NULL. But right now, postgres' parser
rewrites "= NULL" as "IS NULL" for compatibility with certain brain-dead
Microsoft products.
There have been several discussions on pghackers about undoing this bit
of nonstandardness, but so far nothing's been changed. See the
list archives for more detail than you really wanted.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2001-09-16 19:44:00 | Re: Intentional, or bug? |
| Previous Message | Tom Lane | 2001-09-16 19:11:31 | Re: SQL request change when upgrade from 7.0.2 to 7.1.3 |