Skip to content

Ensure surrogate key handles single arg #242

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

Merged
merged 1 commit into from
Jun 29, 2020
Merged

Ensure surrogate key handles single arg #242

merged 1 commit into from
Jun 29, 2020

Conversation

clrcrl
Copy link
Contributor

@clrcrl clrcrl commented Jun 29, 2020

Fixes #241

Updated the tests for this case too

@clrcrl clrcrl requested a review from jtcohen6 June 29, 2020 14:18
Copy link
Contributor

@jtcohen6 jtcohen6 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

Q: Do we need to cut two patch releases (0.3.1 + 0.4.1), to support surrogate_key users who have not yet upgraded to dbt v0.17.0? I'm leaning no, but thought I'd surface it, since this sort of thing will come up again in the future. The OP in #241 is on v0.17.0 so they should have a smooth upgrade from dbt-utils v0.3.0 → v0.4.1.

@clrcrl
Copy link
Contributor Author

clrcrl commented Jun 29, 2020

Oh yikes, I'm leaning no just for simplicity, and so more people upgrade to 0.17.0

@clrcrl clrcrl merged commit 29b4207 into master Jun 29, 2020
@clrcrl clrcrl deleted the fix-surrogate-key branch June 30, 2020 12:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0.3.0 surrogate_key does not support a single string argument
2 participants