-
Notifications
You must be signed in to change notification settings - Fork 137
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
SNOW-1672681: DbUp support #1026
Labels
Comments
sfc-gh-dszmolka
added
the
status-triage_done
Initial triage done, will be further handled by the driver team
label
Sep 20, 2024
hi @bricelam - thank you for raising this with Snowflake and providing the background information. I'll need to confer with my team on this, if it's something which Snowflake realistically wants to do in the near future. Will come back once I have something to share. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
DbUp is a wonderful tool built on .NET for deploying SQL scripts to databases.
The DbUp project maintains a number of providers, but isn't interested in maintaining one for Snowflake.
There have been a couple community-written ones. Viostream/dbup-snowflake was the first one. It was built on top of ODBC. Unfortunately, it appears to be abandoned since 2022. B3zaleel/dbup-snowflake is a fork built on Snowflake.Data (this project), but it also appears abandoned since Feb 2024.
DbUp providers aren't a lot of code (less than 100 lines) and haven't traditionally required a lot of maintenance (about two releases per year).
Would you, the Snowflake.Data team, be willing to take on maintaining a DbUp provider? I'm sure the handful of open-source developers who've dabbled in the past would rally behind this idea.
The text was updated successfully, but these errors were encountered: