Skip to content
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

Merged
merged 4 commits into from
Aug 9, 2022

Conversation

shrodingers
Copy link
Contributor

@shrodingers shrodingers commented May 23, 2022

resolves #5238

Description

Handles varchar the same way as text for postgres columns (since unlimited varchar on postgres is not implicitely limited to 256 characters as on redshift)

Checklist

@shrodingers shrodingers requested a review from a team as a code owner May 23, 2022 08:38
@cla-bot cla-bot bot added the cla:yes label May 23, 2022
@shrodingers shrodingers requested a review from a team as a code owner May 23, 2022 08:39
@shrodingers shrodingers requested a review from emmyoop May 23, 2022 08:39
@jtcohen6 jtcohen6 added the Team:Adapters Issues designated for the adapter area of the code label Jun 1, 2022
@jtcohen6 jtcohen6 added the ready_for_review Externally contributed PR has functional approval, ready for code review from Core engineering label Jun 14, 2022
@emmyoop
Copy link
Member

emmyoop commented Jul 25, 2022

Close/reopen to retrigger snyk

@emmyoop emmyoop closed this Jul 25, 2022
@emmyoop emmyoop reopened this Jul 25, 2022
Copy link
Member

@emmyoop emmyoop left a 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.

.changes/unreleased/Fixes-20220523-103843.yaml Outdated Show resolved Hide resolved
Copy link
Contributor

@McKnight-42 McKnight-42 left a 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!

@shrodingers
Copy link
Contributor Author

Thanks @emmyoop, @McKnight-42 and @jtcohen6 !
Just accepted the changelog update (sorry for the late reply was on holidays)

Copy link
Member

@emmyoop emmyoop left a 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!

@McKnight-42
Copy link
Contributor

@shrodingers great work on this!

@McKnight-42 McKnight-42 merged commit e5ac9df into dbt-labs:main Aug 9, 2022
VersusFacit pushed a commit that referenced this pull request Sep 5, 2022
* 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]>
agoblet pushed a commit to BigDataRepublic/dbt-core that referenced this pull request Sep 16, 2022
* 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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla:yes ready_for_review Externally contributed PR has functional approval, ready for code review from Core engineering Team:Adapters Issues designated for the adapter area of the code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CT-636] [Bug] Postgres unlimited varchar default to varchar(256)
4 participants