corrects inaccuracies in truth tables for AND/OR #287
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AND and OR operators do not take boolean data types as operands — they take boolean expressions, which can return UNKNOWN, but not NULL.
Added some text to explain why the AND and OR tables have the results they do for FALSE AND UNKNOWN and TRUE OR UNKNOWN.
Contributor
|
@NReilingh : Thanks for your contribution to the SQL documentation! The author, @barbkess, has been notified to review your proposed change. |
Contributor
|
@CarlRabeler can you please review. |
Contributor
|
@NReilingh : Thanks for your contribution. It looks great and I'm merging it into the docs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AND and OR operators do not take boolean data types as operands — they take boolean expressions, which can return UNKNOWN, but not NULL.