| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| 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:44:00 |
| Message-ID: | Pine.BSF.4.21.0109161240310.54472-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Mon, 17 Sep 2001, Tod McQuillin wrote:
> 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).
This is because of a hack due to a broken MS client that provided
=NULL for IS NULL in some (possibly small) case. There's a grammar
hack which makes the token sequence = NULL into IS NULL. There's
been talk about making this optional or ripping it out entirely (yay),
see past discussions on this topic for more detail.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2001-09-16 20:36:38 | Re: optimizing queries and indexes... |
| Previous Message | Tom Lane | 2001-09-16 19:31:07 | Re: Intentional, or bug? |