Use SVV_COLUMNS Instead of INFORMATION_SCHEMA.COLUMNS On Redshift #64
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
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.
I've always noticed that my completion never found a certain schema. I think it has something to do with how that specific schema is set up on our DB but I have no idea for sure what it could be since I do have all the permissions and stuff. It turns out that INFORMATION_SCHEMA can't find information about this schema at all, in any of the tables. I wasn't able to track down an answer as to why but I did find that SVV_COLUMNS does find it.
I'm not sure if this is just me or if other Redshift users can't find tables as well. Since I've already made and use the SVV_COLUMNS modifications I decided to just create a variable that defaults to 0 and then make a pull request for you to merge if you like. :)