Fixes translation issue of calculated expression with conditional expressions #377
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.
Some conditional expressions are not translated into SqlCase, but to SqlVariant, at the same time other providers use SqlCase successfully.
This led to wrong result SQL query text in many parts, like ORDER BY, GROUP BY. This happened because instead of entire expression postprocessor as expected chose either of two branches of SqlVariant. For example, for query like
it led to something static value of 2 instead of expression which should be applied to every row in results, similar to this
when correct SQL text should be similar to this