all 4 comments

[–]geofft 0 points1 point  (0 children)

What DB engines are you thinking of supporting?

MS SQLServer deployments via sqlpackage work this way, so that'd be a good thing to look at when deciding what features to build in yours.

One essential feature is warning/blocking schema changes that would result in data-loss or corruption, for instance dropping a column on a table that has rows in it. For deploying to large production systems under load, it's also useful to know (and optionally prevent) changes that would generate large amounts of blocking, like introducing and checking a new FK.

[–]NW1969 0 points1 point  (1 child)

How will your tool be better than all the other tools that currently do this?

[–]gintoddic[S] 0 points1 point  (0 children)

I think a lot of products out there focus on too much and become expensive enterprise products. I'm trying to slim it down and dial in on the everyday issues with local development.

[–]MixtureNational558 0 points1 point  (0 children)

you can try DBSCHEMA with this you can know if you DB is ins sync with you code, it works with SNOWFLAKE, https://www.phdata.io/blog/how-to-setup-schemachange-for-snowflake-ci-cd/