Activity overview
Latest activity by Fredrik_S
Big thank you for your suggestions. Just to make sure I understand, when you say “develop using schema model” do you mean in point my feature branch to the dev environment and use apply to database? Secondly do you recommend generating the migration scripts in the feature branch?
Best regards, / comments
Big thank you for your suggestions. Just to make sure I understand, when you say “develop using schema model” do you mean in point my feature branch to the dev environment and use apply to database...
We user Flyway Desktop Enterprise edition.
Our different environments PROD, QA, and DEV is in SQL Server 2019.
For our individual development databases we use Redgate Clone (data image based on PROD)
/ comments
We user Flyway Desktop Enterprise edition.
Our different environments PROD, QA, and DEV is in SQL Server 2019.
For our individual development databases we use Redgate Clone (data image based on PR...
Our
problem is that we often get development requests that for some reason or other
gets stuck in development and therefore that environment might differ from our
production environment. So, if I generate migration scripts to work for our dev
environment, they may not be suited for our production environment. To minimize
the risk for problems during deployment to production we felt it was easier to
generate migration scripts separately for each environment.
There is also the point that if you have to go
back and forth a lot in an feature you are developing (it did not pass
integration test for example) you end up with multiple migration scripts for
the same feature, but when you come to production all your back and forth
changes gets rolled into one migration script (because what we save an merge is
the schema model) / comments
Our
problem is that we often get development requests that for some reason or other
gets stuck in development and therefore that environment might differ from our
production environment. So, if I g...
we generate migration scripts for each of our environments and save them in there respective branch (dev, qa and main (for prod)). When we create a new feature branch from main it contains the migration scripts generated for our production environment, when we den merge our feature branch into our common dev branch the migration scripts generated for prod are merged into our migration folder for the dev environment. So each environment should have its own set of migrations scripts and the problem is that when we merge in our feature branch int contaminates the environments migration scripts with migration scripts generated for production. / comments
we generate migration scripts for each of our environments and save them in there respective branch (dev, qa and main (for prod)). When we create a new feature branch from main it contains the migr...