Bug Fix for SELECT with uppercase columns (Approach 2) #1419
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
anmolagarwalcp810
changed the title
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.
Problem Statement
Select query for tables with tables with upper case columns wasn't working: Issue 1079
Solution
Removed the part of code where columns were getting converted to lower case. Although this makes select query case sensitive, it resolves the above problem. If this approach doesn't work, then there is another PR from branch users/anmolagarwal/select-bug-fix-approach-1.
Output after Fix
But SELECT has become case-sensitive, so commands like shown below won't work now:
