Options
Subversion Switching
ddchego
Posts: 2
Are there any plans to introduce switching in Subversion to SQL Source Control?
Right now the only way i see to do this is to unlink from the current repository and link to the new repository. This is extra steps having to be done and behind the screens alot of extra bandwidth as on unlink it deletes the data and then has to re download it all on link.
I would imagine that until a conflict editor is built into SQL Source Control it would be difficult to switch where conflicts happen.
Please let me know if this is a requirement and where in the development process it is at.
Thanks
Right now the only way i see to do this is to unlink from the current repository and link to the new repository. This is extra steps having to be done and behind the screens alot of extra bandwidth as on unlink it deletes the data and then has to re download it all on link.
I would imagine that until a conflict editor is built into SQL Source Control it would be difficult to switch where conflicts happen.
Please let me know if this is a requirement and where in the development process it is at.
Thanks
Comments
You're right that dealing with conflicts is going to be one of the key things that govern how switching is dealt with. I think switching is something we'd like to look at in the future although I don't have any timescales to give you I'm afraid.
An option that we currently suggest is creating a separate working database for each branch. That might make things a bit easier for you.
Redgate Software