You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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: