• Sean Lange (4/30/2013)


    Hugo Kornelis (4/30/2013)


    <nitpicking>

    Not NULL - Unknown. Quite different concepts! (NULL means the absence of any data; Unknown is a result in three-valued logic that is the result of attempting to do a comparison with data that is absent)

    </nitpicking>

    My example was a bad one for sure. I am well aware of the three way "boolean" logic in sql.

    The correct wording would be either "first statement/block on true, second (following ELSE) otherwise", or "first statement/block on true, second (following ELSE) on false or unknown".

    I agree. They should just make it "Otherwise". This is actually what happens. For any reason that the condition is NOT true the ELSE block will execute.

    For me, no matter how many ways I try to read the BOL entry it is clear (even given that the reason it is not true is rather ambiguous). Removing the word FALSE in this case would actually add clarity. 😉

    Hugo,

    Question if you have time.

    <furthernitpicking>

    Not NULL - Unknown. Is unknown also called uninitialized?

    </furthernitpicking>

    Just wondering?

    Thanks

    Not all gray hairs are Dinosaurs!