Re: [HACKERS] case bug?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Keith Parks <emkxp01(at)mtcc(dot)demon(dot)co(dot)uk>
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] case bug?
Date: 1999-09-18 19:37:17
Message-ID: 20727.937683437@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Keith Parks <emkxp01(at)mtcc(dot)demon(dot)co(dot)uk> writes:
> Then I tried inserting a NULL into the table, which the
> case statement then treated as 0 and not null.

This is a bug: the test expressions i < 0 etc are actually returning
NULL, but ExecEvalCase is failing to check for a NULL condition result.
It should treat a NULL as false, I expect, just as WHERE does.

regards, tom lane

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-09-18 19:58:06 Why do we need pg_vlock?
Previous Message Tom Lane 1999-09-18 19:31:35 Notice: heap_open/close changes committed