-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix postgres handling for unlimited varchars #5292
Conversation
Close/reopen to retrigger snyk |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good but I'm going to let @McKnight-42 have the final approval.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shrodingers Sorry for how long it's taken to get eyes on this, seems like a super reasonable! great conversation in the issue between you and @jtcohen6 just the minor fix @emmyoop pointed out for changelog and this should be good to merge!
Co-authored-by: Emily Rockman <[email protected]>
Thanks @emmyoop, @McKnight-42 and @jtcohen6 ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thanks for pulling in the requested changes @shrodingers!
@shrodingers great work on this! |
* Fix postgres handling for unlimited varchars * fix: correctly name varchar * chore: added changelog entry * Update .changes/unreleased/Fixes-20220523-103843.yaml Co-authored-by: Emily Rockman <[email protected]> Co-authored-by: Emily Rockman <[email protected]>
* Fix postgres handling for unlimited varchars * fix: correctly name varchar * chore: added changelog entry * Update .changes/unreleased/Fixes-20220523-103843.yaml Co-authored-by: Emily Rockman <[email protected]> Co-authored-by: Emily Rockman <[email protected]>
resolves #5238
Description
Handles
varchar
the same way astext
for postgres columns (since unlimitedvarchar
on postgres is not implicitely limited to 256 characters as on redshift)Checklist
changie new
to create a changelog entry