AW: AW: Re: [SQL] behavior of ' = NULL' vs. MySQL vs. S tand ards - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: AW: Re: [SQL] behavior of ' = NULL' vs. MySQL vs. S tand ards
Date
Msg-id 11C1E6749A55D411A9670001FA687963368333@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
List pgsql-hackers
> -- If I have interpreted SQL92 correctly UNKNOWN IS TRUE should return
> FALSE, and UNKNOWN IS NOT TRUE is equivalent to NOT (UNKNOWN IS TRUE) ==>
> TRUE. Is this correct?

No, I do not think it is valid to say "should return true|false"
I think they should return UNKNOWN. Only when it comes to evaluating the
"... WHERE UNKNOWN;" can you translate it to "... WHERE FALSE;", or in the 
output function.

My interpretation would be:
UNKNOWN IS TRUE         --> FALSE
UNKNOWN IS NOT TRUE     --> FALSE
NOT (UNKNOWN IS TRUE)    --> FALSE

Andreas


pgsql-hackers by date:

Previous
From: "Joe Conway"
Date:
Subject: Re: AW: Re: [SQL] behavior of ' = NULL' vs. MySQL vs. Stand ards
Next
From: Zeugswetter Andreas SB
Date:
Subject: AW: AW: Re: [SQL] behavior of ' = NULL' vs. MySQL vs. S tand ards