Comments
Sort by recent activity
Thank you for your response @Kurt_M ! Let me try and provide the scenario more clearly:
My team member has a new feature to work on that requires a table drop. We'll call this feature A and the table TableA.
They clone the master branch from the remote repository and checkout a new feature branch feature/A.
They link feature/A to their database via RedGate SSC
They run a script to drop TableA from SSMS.
When they go to Commit this change to feature/A they are able to see a change type of Drop for TableA. They commit the drop or TableA to feature/A and push feature/A to the remote.
Now I come along and need to take their change from feature/A:
I clone the master branch from the remote repository
Checkout branch feature/A
Link feature/A to my database (I still have TableA in my database)
Go to the "Get Latest" tab
No Drop change type exists for TableA
My thought would be in linking feature/A to my database and looking at Get Latest it would see that I have a table in SSMS that no longer exists in feature/A and would put this in the Get Latest list for a drop change type. This feels like it would be a pretty common scenario for any development team so I'm left wondering if there is something fundamental about SSC that I'm missing here... / comments
Thank you for your response @Kurt_M ! Let me try and provide the scenario more clearly:
My team member has a new feature to work on that requires a table drop. We'll call this feature A and the tab...