Fix: redshift explain verbose no where limit#2239
Merged
izeigerman merged 4 commits intomainfrom Mar 11, 2024
Merged
Conversation
izeigerman
changed the title
georgesittas
approved these changes
Mar 8, 2024
tobymao
reviewed
Mar 9, 2024
Collaborator
Author
There was a problem hiding this comment.
This covers the most common Redshift types as per https://docs.aws.amazon.com/redshift/latest/dg/c_Supported_data_types.html. We'll add more later if needed
tobymao
reviewed
Mar 9, 2024
tobymao
approved these changes
Mar 9, 2024
izeigerman
force-pushed
the
fix-redshift-explain-verbose-no-where-limit
branch
from
579b361 to
1e1594e
Compare
izeigerman
force-pushed
the
fix-redshift-explain-verbose-no-where-limit
branch
from
1e1594e to
3a10f21
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
No description provided.