fix: Issue #2109 true and false value parsed as column instead of BooleanValue #2110
Conversation
This file contains 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
…ead of BooleanValue
|
Very clean, well done! Thank you for your help and contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi all,
this patch addresses Issue #2109 in the JSQLParser library, where TRUE and FALSE were incorrectly handled as column names rather than as boolean values.
According to the SQL standard ISO/IEC 9075:2016, TRUE and FALSE are reserved keywords representing boolean literals, not column identifiers.
This patch updates the parser to recognize TRUE and FALSE as boolean literals, ensuring compliance with the SQL standard and preventing potential errors in query interpretation.
Ciao,
Luca