Add support for Aliases on CASE expressions #203
Merged
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
This PR allows CASE expressions to be aliased to fix issues #192 and #162
It specifically adds support for
CASE ... END [AS] aliasfor both CASE formats with theASkeyword being optional.Im a little out of my depth so any help or guidance tests or functionality that I have missed would be great.
I know that queries like
CASE ... END expression [AS] aliassuch asSELECT CASE WHEN 2 IS NULL THEN 0 ELSE 2 END + 1 as 'foo'are not covered. Let me know if there is sufficient use-case for this scenario and I'll attempt it in a new PR