Propagate ExpectedType to CaseNode in hql #2705
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
bahusoid
changed the title
maca88
approved these changes
Mar 18, 2021
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.
Fixes #2704
The following expression
x.IsChiusa == !noIn 5.2 is generated simply as
alias.IsChiusa=@p0(@p0is set to!no)In 5.3 is generated as
alias.IsChiusa=case when not (@p0='S') then 1 else 0 end(@p0is set tono). Where1and0are invalid values insidecasestatement, asIsChiusais string column.Not sure what causes different query (maybe #2335) but provided fix makes sure that constants inside
casestatement are properly translated for custom type