| From: | Markus Schaber <schabi(at)logix-tt(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: bug or feature, || -operator and NULLs |
| Date: | 2006-10-20 13:10:05 |
| Message-ID: | 4538CAAD.4060207@logix-tt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi, Martijn,
Martijn van Oosterhout wrote:
> On Wed, Oct 18, 2006 at 11:36:44AM -0700, Jeff Davis wrote:
>>> What's being suggested simply violates common sense. Basically:
>>>
>>> if (a = b) then (a||c = b||c)
>>>
>> If a is 'x' and b is 'x' and c is NULL, the above statement doesn't hold
>> in PostgreSQL.
>
> Heh, well, c is supposed to be not NULL. Missed that. I was using the
> equals to include (NULL = NULL) but in SQL it's not like that.
Maybe you should replace "=" with "IS NOT DISTINCT FROM" :-)
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schaber | 2006-10-20 13:19:32 | Re: Multiple postmaster + RPM + locale issues |
| Previous Message | Alvaro Herrera | 2006-10-20 12:47:28 | Re: Asynchronous I/O Support |