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
We use Schemachange for deploying into all of our environments (DEV, STG, and PRD). We have been running into timing issues with R__ scripts causing them to be reverted to a previous version. Example below.
For example Developer A is working on R__Some_Stored_Proc.sql and has had Schemachange deploy it into Dev. Developer B is working on an entirely unrelated script but doesn't have the changes Developer A made. When Developer B deploys their changes it reverts R__Some_Stored_Proc.sql to the previous version since the checksum is different.
These two devs will end up going back and forth until we are fully merged and synced up. Not an issue for Production environments, but it would be useful for us to isolate what scripts were being checked in our DEV and STG environment.
Could you look a the PR you raised and help us resolve the merge conflict with the latest version of Schemachange and help close this issue accordingly. If I misunderstood this issue, please let me know.
We are in the process of reviewing the issues and PRs.
We use Schemachange for deploying into all of our environments (DEV, STG, and PRD). We have been running into timing issues with R__ scripts causing them to be reverted to a previous version. Example below.
For example Developer A is working on R__Some_Stored_Proc.sql and has had Schemachange deploy it into Dev. Developer B is working on an entirely unrelated script but doesn't have the changes Developer A made. When Developer B deploys their changes it reverts R__Some_Stored_Proc.sql to the previous version since the checksum is different.
These two devs will end up going back and forth until we are fully merged and synced up. Not an issue for Production environments, but it would be useful for us to isolate what scripts were being checked in our DEV and STG environment.
I put in PR 145
The text was updated successfully, but these errors were encountered: