Bug: drop database and then recreate causes conflicts
I have a database managed in SVN. On my development machine I deleted it and then recreated it with the same name. RedGate maintained the link to SVN despite the drop (ok, doesn't bother me) but it then marked every object in the database as being in conflict
This is a known issue. I’m glad you’re ok that the link to SVN is maintained. The problem is the underlying working folder is out of date.
WORKAROUND:
Option 1)
On the setup tab, unlink the db from source control. If you still want to manage the db in SVN, then relink.
Option 2)
Use the Commit or Get Latest tabs to decide if you want to keep the version in your db and commit it or take the version that is in source control. After making a decision using the radio buttons in the differences pane at the bottom of these tabs, you must then click the Commit and/or Get Latest buttons to actually perform the action.
HINT: You can select multiple rows by selecting 1 row and then hitting Ctrl-A or select the top row and then hold the shift key down and select the last row with your mouse. The decision to Keep Mine or Take Theirs will then apply to all the hightlighted rows.
I hope this helps!
-
lakeland commented
Thanks, that's a good workaround.